Open JFolberth opened 1 year ago
To illustrate a little more I did find a workout around using the Azure CLI for the deployment:
- name: Deploy ARM Template
uses: azure/CLI@v1
with:
inlineScript: |
az deployment group create --resource-group ${{ inputs.resource-group-name }} --template-uri ${{ format('{0}?{1}', 'https://saadf1234deveus.blob.core.windows.net/templates/linkedTemplates/ArmTemplate_master.json',env.SAS_TOKEN) }} --parameters ${{ format('{0}/{1}?{2}', 'https://saadf1234deveus.blob.core.windows.net/templates/datafactory/cicd-parameters', inputs.arm-template-parameters-file, env.SAS_TOKEN) }}
Seeing the arguments are the same I feel confident this is a bug in how the arm action is interpreting the values passed into parameters
@bishal-pdMSFT Any update on this. Feels like this is a big issue.
I believe there is a bug when passing in values to the
parameter
argument. My scenario is I am deploying Data Factory w/ Linked ARM templates. As part of this deployment I am :I am seeing an issue when the ARM deployment executes that the template file w/ the URL for the storage account and including the SAS key works. This same method does not work with the parameters and it appears it is stopping on the '=' in the SAS key and thinks this is an override to an ARM parameter in the template.
Link to my action: https://github.com/JFolberth/adf-cicd-demo/actions/runs/5207084212/jobs/9394295417
Here is the code: