Fix incorrect handling of cluster state vs regState, log cleanup #1314
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… into log-cleanup
carrolp
changed the title
adamkingit
reviewed
Apr 25, 2023
adamkingit
approved these changes
Apr 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix cluster
stateso that it always reflects active or inactive if the cluster has ever successfully reported updates via watch-keeper, instead of (usually temporarily) revertingstagetoregisteredmerely by enabling the registration url (enableRegistrationUrlmutation to view the script).Also removes some excess logging and potential logging of sensitive values in some error-handling scenarios.