docs(gcp-backplane): record why GCP subjects are not scoped to a single BBD - #292
Merged
Merged
Conversation
…le BBD GCP is the only backplane family that scopes workload identity federation to the workspace rather than to one building block definition. That looks like an oversight next to azure/aws/stackit, so write down that it is a decision: the uuid cannot be pinned without closing a Terraform dependency cycle, and the workarounds cost more than the hardening is worth for definitions owned by one platform team. Closes the question raised in #291, which is not being pursued. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Scorecard CheckNo module changes detected relative to |
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
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.
Follow-up to #291, which is closed and not being pursued.
GCP is the only backplane family that scopes workload identity federation to the workspace rather than to one building block definition. Next to
modules/azure/,modules/aws/andmodules/stackit/— all of which pin the definition uuid — that reads as an oversight. It is a decision, so this writes it down.The note goes in
.agents/references/gcp-backplane.md, directly after the subject-derivation idiom, and covers:credentials_json— whose audience is that same pool provider's resource name.startsWithadmits any definition owned by the same platform workspace, but authoring a definition there is already a privileged action that coincides with being able to change the backplane itself. Residual cost is audit attribution.Docs only — no module or scorecard behaviour changes.
The underlying limitation is going to meshStack product separately, as a request to make a definition's WIF subject knowable before the definition exists.
🤖 Generated with Claude Code