docs: state-file deploy + prod-promotion procedure in AGENT.md - #88
Merged
Conversation
Viaduck now deploys via the charts state-file mechanism (same as duckgres and millpond): release dispatch -> state/viaduck.yaml -> dev auto-promotes, prod behind the prod-promote-managed-warehouse approval gate. Documents the resolve/delta/fire/approve/verify procedure and that the viaduck-metrics Deployment runs the millpond image at millpond's prod pin (deploys through millpond promotions).
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.
Summary
release.yamlbuilds + dispatchescommit_state_update→state/viaduck.yaml→ dev auto-promotes; prod only via the chartspromote-to-prod.ymlworkflow behind theprod-promote-managed-warehouseapproval gate.viaduck-metrics(viaduck namespace) runs the millpond image at millpond's prod pin — it deploys through millpond promotions, not viaduck ones.Testing
Docs-only:
just lock-check fmt-check lint docs-checkgreen (code-path CI steps unaffected).