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

Configservice Healthmanager Integration #1317

Conversation

BehnamMozafari
Copy link
Contributor

  • Integrate ConfigService with HealthManager
  • Instance is set to unhealthy if config is not retrieved from the core endpoint after 3 consecutive attempts
  • Instance set back to healthy once config retrieval is successful

- instance is unhealthy when initial config not retrieved
- ConfigService set to healthy in configuration processor
- ConfigService set to unhealthy in configStream exceptionHandler
…-4678-configservice-healthmanager-integration

# Conflicts:
#	src/main/java/com/uid2/operator/service/ConfigService.java
- Refactor Const names in Const.Config
- Update ConfigValidatorUtil log messages
- Set to unhealthy after 3 consecutive failed retrievals
Base automatically changed from bmz-UID2-4606-runtime-config-application to main February 3, 2025 05:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants