fix(certificatee): quiet unmanaged vault certificates#40
Draft
ananthb wants to merge 1 commit into
Draft
Conversation
ananthb
force-pushed
the
codex/certificatee-quiet-unusable-vault-certs
branch
from
90b2249 to
0f4584e
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
Why
Staging has HAProxy-loaded certificates that are intentionally unmanaged or have live certs newer than Vault.
v0.5.3correctly refuses to roll those back, but the current behavior turns that into per-cert error noise and incrementscertificatee_certificates_update_failures_totaleven when the live cert is not near expiry.No Linear ticket - rollout follow-up.
Validation
/usr/local/go/bin/go test ./cmd/certificatee/usr/local/go/bin/go test ./...