Repository navigation
fix(no-release): harden infra operator contracts - #29
Merged
Merged
Conversation
justgithubaccount
force-pushed
the
fix/infra-contracts-issue-28
branch
from
October 30, 2026 10:09
db6a60a to
45b6e79
Compare
justgithubaccount
marked this pull request as ready for review
October 30, 2026 10:29
This was referenced Oct 30, 2026
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
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.
Closes #28
Summary
nodes, guard the versioned GitOps root, and render the Argo CD chart once before a same-render retryseal:postgree, and preserve its existingchat-postgreeSecret nameCompatibility and rollback
scripts/check-nodes.shkubectl get nodes -o widemainfor the Kubernetes rootapp-poly-gitops-k8s@v1.5.0rootmainmain: the only existing tag,v0.1.0, itself points back tomainchat-postgrestask plus legacychat-postgreeentrypointKEY=valueform is intentionally not retained because it leaks via process listingsExternal/manual callers cannot be proven absent, so both
argocd-sync-check.shandseal:postgreeremain compatibility entrypoints. The optional SealedSecret path is retained and is not called by active dev/smoke workflows.Validation
-backend=false -input=false, and validatemain: no self-management desired-state deltachat-postgreeand default/explicit kubeconfig behaviorNo cloud workflow, live paid smoke, deployment, Terraform plan/apply/destroy, release, or Kubernetes operation was run.