compose: show resources#4914
Conversation
be05658 to
ab759b9
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
|
|
|
Thinking through the experience:
These two options very different results despite being the same command. It also feels like it's stretching the definition of "show" usually,
These commands come with a matching list command that lists the available items that can be specified in show:
That way you can run 'az containerapp list' to see all the options then run
|
Fix `AZURE_OPENAI_ENDPOINT` not showing in add preview. In #4914, we shifted the preview to leverage the newly added resource metadata. Azure OpenAI models had a resource specific show implementation built that wasn't immediately refactored in the change. This change shifts the Azure OpenAI implementation and fixes the add preview. Contributes to #4933




Add ability to
azd show <name>for all existing supported resources.With this change, we add the ability to display fully-evaluated connection variables for resources without provisioning a
hostresource.To do this, we create a generic mapping between ARM and the app representation. This mapping, which is comprised of simple templating-like expressions, are evaluated against live Azure in the
showcommand.Example output:

Forward-looking ideas
This contributes to compose: existing resource support #4577, in which
azd show <full resource ID>could be used to display, or as a base layer, for obtaining connection information to an existing resource. The schema does not track managed identity vs key-based approaches, but I do see a somewhat straightforward pathway there.This also contributes to compose: explicit mapping #4747, as we are laying down a schema mapping that could be used to emit Bicep representation during generation. This may end up unifying the story between generation and evaluation for roundtripping.
This also contributes to compose: explicit mapping #4747. we expect to use parts of the parsing logic in to support a similar expression-model at the app layer.
Closes #4727
Contributes to #4577, #4747, #4887