Closed nb-atudose closed 1 year ago
Hi @nb-atudose! The reason for this the UI creation scenario is only able to know about parameters specified in the manifest file. If you add the parameters that you see in the ARM template to the manifest, that data can be input via the UI.
Here is an example of a manifest.yml with some basic parameters:
name: AppConfig
summary: This is an App Configuration deployment.
description: Deploys an App Config.
templatePath: azuredeploy.json
parameters:
- id: "name"
name: "name"
description: "Name of the App Config"
default: ""
type: "string"
required: false
- id: "location"
name: "location"
description: "Location to deploy the environment resources"
default: "[resourceGroup().location]"
type: "string"
required: false
runner: arm
Thank you! It would be a good idea to specify this in the documentation :grin:
Instead of displaying the parameters for a catalog item that requires parameters, this message is shown: This catalog item requires no parameter inputs, and will be created immediately.
The catalog item does require parameters:
Deploying from az cli works as expected.