Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[API] GET /v3/config/paths/list no longer return path name #2517

Closed
1 of 13 tasks
tbnguyen1407 opened this issue Oct 17, 2023 · 2 comments
Closed
1 of 13 tasks

[API] GET /v3/config/paths/list no longer return path name #2517

tbnguyen1407 opened this issue Oct 17, 2023 · 2 comments

Comments

@tbnguyen1407
Copy link

Which version are you using?

v1.2.0

Which operating system are you using?

  • Linux amd64 standard
  • Linux amd64 Docker
  • Linux arm64 standard
  • Linux arm64 Docker
  • Linux arm7 standard
  • Linux arm7 Docker
  • Linux arm6 standard
  • Linux arm6 Docker
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (please describe)

Describe the issue

Updated API no longer return path name when listing paths. API docs still show all fields. This makes it impossible to see path details since name is not shown.

Describe how to replicate the issue

  1. start the server
  2. create a path
  3. call API to list paths. No item/path name is returned
GET /v3/config/paths/list

{
  "itemCount": 1,
  "pageCount": 1,
  "items": [
    {
      "source": "mysourcehere"
    }
  ]
}

Did you attach the server logs?

no

Did you attach a network dump?

no

@tbnguyen1407
Copy link
Author

Sorry after going through the API docs again, I see 2 different APIs

GET /v3/config/paths/list
GET /v3/paths/list

which return different results and a bit confusing. 2nd API is what I need. Closing this now.

Copy link
Contributor

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant