-
Notifications
You must be signed in to change notification settings - Fork 218
WIP: Prompt user to select or create new resource #4418
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
Conversation
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
1e210fc
to
f141875
Compare
Why a new bicep type i.e., |
Hi @wbreza. 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. |
Hi @wbreza. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing "/reopen" if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the "no-recent-activity" label; otherwise, this is likely to be closed again with the next cleanup pass. |
Authoring bicep templates that work well across a wide range of scenarios is hard. One difficult scenario is supporting a bicep module where the resource is conditionally created based on whether the consumer wants to use a new resource or leverage an existing resource.
We are seeing this scenario multiple times in various AI use cases where customers may already have AI studio hubs, projects already created or want to leverage existing services like an Azure Open AI Service, etc.
Idea
Leverage custom
azd
metadata within bicep to enable authors to mark up parameters that map to a new or existing resource using bicep user defined types.Example of user defined type
Then when specifying a bicep parameter additional
azd
metadata can be added to light up new experiences inazd
Example of using parameters with custom metadata
azd
ExperienceWhen calling
azd provision
users will automatically be prompted to select a resource if this is the first time they are deploying the project.The data for the custom input is serialized and sent in as bicep input parameters
The provisioning continues as normal and is up to the author of the bicep to ensure they reuse or create the resource based upon the input value.