feat: add Foundry project infrastructure - #9560
Draft
Hui Miao (huimiu) wants to merge 1 commit into
Draft
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). 20 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
microsoft-github-policy-service
Bot
added
the
no-recent-activity
Contributor
|
Hi @Hui Miao (@huimiu). Thank you for your interest in helping to improve the Azure Developer CLI experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
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.
Why this is needed
Foundry infrastructure ejection must coexist with existing user infrastructure. Without explicit planning, a project can overwrite paths, lose provider information, or leave a partial ejection behind.
Approach
Add Projects-side infrastructure planning and installation for Bicep and Terraform. The implementation validates paths, providers, modules, layers, and collisions before staging changes, then updates project configuration atomically with rollback support.
Scope
This draft contains only the Projects infrastructure and hardening changes. Agents delegation and recording-proxy changes are separate drafts.
Dependency
This draft is based on #9559. After that PR is merged and its base branch is deleted, GitHub can retarget this PR to
main.