Override Parameters not working for Custom ARM-Template Parameters

Question

We added the Template-Parameters-Definition.json file to the root of our collaboration branch in order to expose additional parameters in the TemplateParametersForWorkspace.json ARM-template file. This seemed to work, we exposed a new parameter for linked services named like linkedservicename_properties_parameters_dbServerName.

To override this parameter during a release:

1. We added a secret to a key-vault named something like UA-linkedservicename-dbServerName.
2. Added this secret to a variable group.
3. Attached the variable group to a release pipeline.
4. Added -linkedservicename_properties_parameters_dbServerName $(UA-linkedservicename-dbServerName) to the overrideparameters section of the workspace deployment task within the release pipeline.

We followed the same steps as we did when adding other override parameters. However, when the release pipeline runs, the secret is downloaded, but the override does not work. The linked service is left in a "failed" state. The dbServerName parameter default value is blank. And its parameter type is blank. And when we test the connection, it fails.

Any ideas why the custom ARM-template parameters cannot be overridden?

Answer 1

@Steven Vance Thanks for using MS Q&A platform and posting your query.

There could be several reasons why the custom ARM-template parameters cannot be overridden. Here are a few possibilities:

1. Parameter Data Type: Each parameter in an ARM template must be set to one of the data types. If the dbServerName parameter type is blank, it might be causing the issue. Make sure to specify the correct data type for your parameter.
2. Parameter Declaration: At a minimum, every parameter needs a name and type. If the dbServerName parameter default value is blank, it might be causing the issue. You can specify a default value for a parameter. The default value is used when a value isn’t provided during deployment.
3. Path Issue: The error could be due to the incorrect path set for the override template parameter. Make sure that the path you’ve set is correct and the files are present at that location.
4. Quotes around Value: If the value you’re passing for the override parameter is not in JSON format, it might cause an error. Try adding quotes to your value.
5. Manual Parameter Setting: If the parameters are not recognized automatically, you might need to set them manually one by one.

Hope this helps. Do let us know if you any further queries.