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.

Sign up for GitHub

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

Jump to bottom

goProbe query API missing "/_query" endpoint & broken config file handling #340

Closed
fako1024 opened this issue Aug 14, 2024 · 0 comments · Fixed by #341
Closed

goProbe query API missing "/_query" endpoint & broken config file handling #340

fako1024 opened this issue Aug 14, 2024 · 0 comments · Fixed by #341
Assignees
@fako1024
Labels
bug Something isn't working

Comments

@fako1024
Copy link
Collaborator

It seems that one of the recent changes (probably #309) introduced to regressions:

  • The goProbe direct API doesn't provide a /_query endpoint anymore, only the validation ones. The distributed API has all three available (probably a copy/paste mishap)
  • Even after restoring that, the query via API will always attempt to query the DB at the default location in /usr/local/ (cause by a race condition in assignment of the DB path, which now happens after the endpoints are registered)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fako1024 fako1024

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[bugfix] Fix missing query route and DB path parsing in goQuery API els0r/goProbe
1 participant
@fako1024