fix: Register healthcheck endpoint for security-proxy-auth #4426
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
secuity-proxy-auth was not registering /api/v2/ping endpoint (nor version nor config) common endpoints. This was causing the service to appear unhealthy in consul, as the snap was starting the service with --registry flag.
PR Checklist
Please check if your PR fulfills the following requirements:
BREAKING CHANGE:
describing the break)Testing Instructions
Apply edgexfoundry/edgex-compose#350 or run the snap, and verify the service health in consul.
New Dependency Instructions (If applicable)