-
Notifications
You must be signed in to change notification settings - Fork 218
WIP: compose with existing infra #5088
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
6b96d56
to
dd108d9
Compare
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
5bcb68c
to
15757a0
Compare
This change allows for composability to work with an existing
infra
directory unmanaged by azd.Infra provisioning. The provisioning engine has been updated to serially provision the root
./infra
, then./infra/app
if it exists. The following behavioral changes have been applied:Composability synth. The synthesized infra directory has a
.azd
file to serve as a sentinel. If.azd
exists in a directory, i.e../infra/foo
, it means the directory./infra/foo
is "azd managed". This used to achieve the following behavior when runninginfra synth
:./infra/.azd
exists, we overwrite./infra
../infra/app
.UX
Provision:

Fixes #4578, Contributes slightly to #4755