Skip to content

fix(certificatee): match haproxy certs by SAN#38

Merged
ananthb merged 1 commit into
masterfrom
codex/certificatee-clean-legacy-certs
Jul 4, 2026
Merged

fix(certificatee): match haproxy certs by SAN#38
ananthb merged 1 commit into
masterfrom
codex/certificatee-clean-legacy-certs

Conversation

@ananthb

@ananthb ananthb commented Jul 3, 2026

Copy link
Copy Markdown
Member

Summary

  • collect Vault lookup candidates from live HAProxy SANs, then filename fallback
  • require the selected Vault certificate DNS names to match the full live HAProxy SAN set before writing
  • update the exact HAProxy certificate name already present instead of creating or deleting aliases
  • keep filename fallback for certificates without SAN metadata
  • add coverage for multi-SAN matching and sanitized/legacy filename replacement behavior

This means an existing HAProxy certificate such as certs/_.nodes.rpcpool.com.pem or certs/__nodes_rpcpool_com.pem is replaced in place after certificatee finds a Vault bundle whose SAN set matches the live HAProxy certificate.

No Linear ticket - incident follow-up.

Validation

  • /usr/local/go/bin/go test ./...
  • git diff --check

@ananthb ananthb force-pushed the codex/certificatee-clean-legacy-certs branch from a50f4b2 to f3cb90b Compare July 3, 2026 18:05
@ananthb ananthb force-pushed the codex/certificatee-clean-legacy-certs branch from f3cb90b to 2ef4c3f Compare July 3, 2026 18:08
@ananthb ananthb merged commit a002248 into master Jul 4, 2026
1 check failed
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.

1 participant