Fix Bicep deployment lookup across projects - #9490
Draft
Victor Vazquez (vhvb1989) wants to merge 1 commit into
Draft
Fix Bicep deployment lookup across projects#9490Victor Vazquez (vhvb1989) wants to merge 1 commit into
Victor Vazquez (vhvb1989) wants to merge 1 commit into
Conversation
Tag standard ARM deployments with project identity and prefer project-specific deployment history while retaining a legacy fallback for existing environments. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f8fec20-564b-4f35-8720-6c8f88bc9f08
|
Azure Pipelines: Successfully started running 1 pipeline(s). 21 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
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.
Summary
azd-project-nameidentity resolved fromazure.yaml.nameor the project directoryFixes #8701
Migration behavior
Existing deployments without
azd-project-namecontinue to use the previous newest-deployment fallback. The first provision with this version cannot reuse a legacy deployment's cached state, so it writes a project-tagged deployment and future lookups become unambiguous. Each colliding project/environment must be provisioned once to complete migration.Deployment stacks intentionally retain their existing identity behavior because changing stack names would create a second owner for resources managed by an existing stack.
Validation
go test ./pkg/infra/... ./pkg/azapi -count=1go build ./...Full
mage preflightwas not completed because golangci-lint 2.11.4 remains CPU-bound indefinitely when multiple package roots run together; the same linters pass when isolated by package/analyzer.