-
Notifications
You must be signed in to change notification settings - Fork 742
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
VSCode Extension v0.12.1 and above - ARM template build adds API version for AutomationAccount #9506
Comments
Tested v0.13.1 VS Code extension as well and still has the same problem. |
@JCoreMS This is a deliberate change we decided to make, and we are not planning to switch back to the old behavior. The root cause of this issue is that the PUT response and GET response for To fix the issue, the Automation RP will need to update their service to return the -automationAccount.properties.uri
+reference(automationAccount.name, '2018-06-30').uri |
@shenglol I tried the above approach but got a template validation failure. Any idea when the Automation RP will update their service? It seems like this should have been a coordinated change to ensure we don't impact functionality of existing deployments that have been developed. |
Could you let me know what the template validation failure is? I don't know if there's an ETA for the Automation RP to fix the behavior. @alex-frankel do we have any plan to sync with the Automation RP to discuss the issue? |
It would be interesting to test whether the |
This worked for me |
Related issue: Azure/bicep-types-az#2076 |
Hello @anthony-c-martin, |
You don't need to change anything in your .bicep files, you just need to turn the feature on - see https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-config#enable-experimental-features |
Bicep version
v0.12.1 and above - Issue Noted
v0.11.1 and below - working as expected
Describe the bug
Bug in VSCode Bicep v0.12.1 and above.
These snippets are from my AVD Alerts GitHub Repository:
https://github.com/JCoreMS/AVDAlerts
\deploySubscription\solution.json (Current version is v0.11.1 and working)
v0.12.1 and above (Not Working)
"uri": "[reference(resourceId('Microsoft.Automation/automationAccounts/webhooks', parameters('AutomationAccountName'), format('{0}_{1}', parameters('RunbookNameGetStorage'), dateTimeAdd(parameters('Timestamp'), 'PT0H', 'yyyyMMddhhmmss'))), '2018-06-30').uri]",
v0.11.1 (Working)
"uri": "[reference(resourceId('Microsoft.Automation/automationAccounts/webhooks', parameters('AutomationAccountName'), format('{0}_{1}', parameters('RunbookNameGetStorage'), dateTimeAdd(parameters('Timestamp'), 'PT0H', 'yyyyMMddhhmmss')))).uri]",
To Reproduce
Steps to reproduce the behavior:
Compile BICEP from AVD Alerts or with nested deployments for an Automation Account with VS Code's BICEP extension version 0.12.1 or above incorporating a webhook. When deploying an automation account and runbook with HTTP and using a webhook, the webhook URI isn't captured and thus empty for the URI for the HTTP action in the workflow.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: