-
Notifications
You must be signed in to change notification settings - Fork 170
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
handle user-defined type as outputs #2805
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - Thanks for the dogfooding and the fix! All the bicep wizards in the world will be singing your praises, @vhvb1989!
Co-authored-by: Wei Lim <weilim@microsoft.com>
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSIContainer
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
Continuation of: #2793
As I was testing the new provision-state with
.bicepparam
files, I also used some user-defined types and got an error when using the types for the outputs.This PR applies the same patch to outputs as we did before for input parameters.
The only difference is that for
outputs
we only need to resolve thetype
, while keeping the value and metadata.This PR also adds a few more update to the input parameters:
metadata
from user-defined type and parameter. This is required to allow folks to useazd
metadata from user-defined types, likeIn this example, both
someLocationA
andsomeLocationB
will have the azd metadata for prompting for location in azd-way.Then, on parameter can add more metadata or override values from the user-defined type like
In this case,
someLocationA
is just appending one more field to the metadata, whilesomeLocationB
is overriding one of the fields.