Repository navigation
release: v1.3.0 to prd - #239
Merged
Merged
Conversation
…ted-usage alert off)
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.
Release
v1.3.0toprd. Part of #173.This PR changes what
prddeploys. Nothing is applied by merging it: the apply runs afterwards, unit by unit, following the release runbook.Changes
release/prd.yaml:v1.2.0→v1.3.0, promoted by digest fromdev-0dcd306(the currentmain). All six images were built at that commit, deployed to dev and passedesmeralda verify --env dev(gateway probes, registry egress, specialist and orchestrator queries),verify --partnerandesmeralda build --verify --env dev.envoy-gatewayis listed because promotion requires every Layer 5 image;prddoesn't deploy Envoy.infrastructure/live/prd/env.yaml:legacy_shared_invoker = truefor the native Agent Identity rollout, phase A (additive: the shared invoker stays until both agents run the new images). A follow-up PR sets it back tofalse(phase B).infrastructure/live/prd/layer-4-governance/terragrunt.hcl:alert_on_unattributed_usage = falseinprdwhile verified attribution (attribution.caller_guard) is off, so the alert doesn't page on normal traffic.Checks
make test-all(unit tests, guards, Terraform validation, gateway harness, Apigee conformance) passes.esmeralda guard --diff origin/main...HEADpasses.esmeralda plan --all --env prdat this commit matches the expected changes listed in Releasev1.3.0toprd#173 (no unexpected destroy or replace, no notification channel change).After merge
Layers 1–2, then Layer 4 (runaway-loop alert first),
iap-egress, identity phase A (Layer 3, MCP services, specialist, orchestrator), then phase B in a follow-up PR.verify --env prdafter each group, then tagsv1.2.0(backfill) andv1.3.0and the GitHub release.