-
Notifications
You must be signed in to change notification settings - Fork 213
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
compose: Add azd add
support for storage accounts (blob service)
#4765
base: main
Are you sure you want to change the base?
Conversation
azd add
support for storage accountsazd add
support for storage accounts (blob service)
azd add
support for storage accounts (blob service)azd add
support for storage accounts (blob service)
56ab02f
to
7e4d801
Compare
4ca15bf
to
2a41e16
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
|
@SophCarp spot on with all the UX improvements, we'll want to address each one.
Just noting this for @JeffreyCA that I'll take a pass to enable We may also need to adjust the "Environment variables" section to display the "standard variables" that the user can use after provisioning. This is now possible with the design direction in #4746. |
Thanks for the feedback!
I created #4774 to track this. It seems to only occur on Windows, and is affecting other confirmation prompts as well. Do we want |
You are indeed right, and part of my goal is to make this a generic HTTP rest call that skips the SDK dependency to scale (and why we haven't added support for other resources) -- we want the Bicep authoring to be the central focus of adding a resource right now. I'm starting work on this pretty soon, but feel free to share the private branch with the work if you'd like. |
I see, I'll leave the |
cc: @SophCarp |
a5d03ba
to
84501cb
Compare
Closes #4716
This PR adds
azd add
support for storage accounts (blob service). These changes allow only one storage account resource to be added. The app is set up to connect to the storage account using keyless authentication. The "Storage Blob Data Contributor" role assignment is given to the local user and the user-assigned identity.azure.yml
supports multiple blob container names andazd provision
will create them, but theazd add
experience will only add one blob container for now.TODO
azure.yaml schema
Binding variables
AZURE_STORAGE_ACCOUNT_NAME
- Storage account nameAZURE_STORAGE_BLOB_ENDPOINT
- Storage account blob endpointDemo
azd.add.storage.mp4