Error deploying parameterized connections.json
See original GitHub issueDoes this occur consistently? Yes
- create entry in connections.json
"managedApiConnections": {
"azurefile": {
"api": {
"id": "/subscriptions/@parameters('SubscriptionId')/providers/Microsoft.Web/locations/germanywestcentral/managedApis/azurefile"
},
"authentication": {
"parameter": "@appsetting('BMVSTORAGE_KEY')",
"scheme": "Key",
"type": "Raw"
},
"connection": {
"id": "/subscriptions/@parameters('SubscriptionId')/resourceGroups/xxx-stage/providers/Microsoft.Web/connections/azurefile"
},
"connectionRuntimeUrl": "https://sss.03.common.logic-germanywestcentral.azure-apihub.net/apim/azurefile/xxx",
"displayName": "storage1"
}
},
Action: azureLogicAppsStandard.deploy Error type: Error Error Message: Error in creating access policy for connection in reference - ‘azurefile’. Error: Error in getting connection - /subscriptions/@parameters(‘SubscriptionId’)/resourceGroups/—/providers/Microsoft.Web/connections/azurefile. Error: The provided subscription identifier ‘@parameters(‘SubscriptionId’)’ is malformed or invalid.
Version: 1.0.12 OS: win32 OS Release: 10.0.22000 Product: Visual Studio Code Product Version: 1.64.2 Language: de
Call Stack
extension.bundle.js:2:4376961extension.bundle.js:2:4376961
rejected extension.bundle.js:2:4372108
processTicksAndRejections task_queues.js:93:5
The same works when editing connections.json in Azure portal.
AB#16678677
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:12
Top Results From Across the Web
Unable to parameterize the connection.json from VS code
while trying to deploy the Logic app from VS code, I am getting Error as below . But same is working fine from...
Read more >Unable to parameterize the connection.json from VS code
while trying to deploy the Logic app from VS code, I am getting Error as below . But same is working fine from...
Read more >Unable to connect the API connection to the logic App via ...
1 Answer. It is an expected behaviour , if you deploy the ARM Template, your both API Connections will have been created but...
Read more >Configure your environment | Cloud Functions for Firebase
This provides strongly-typed environment configuration with parameters that are validated at deploy time, which prevents errors and simplifies debugging.
Read more >Distributed Applications and Interoperable Systems: 17th ...
Desired deployment configuration for our development build. ... Parametric. Interfaces ... such as connection problems, timeouts, and critical faults.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@sven5 I was facing exactly same issue, referencing subscription and resource group from app settings directly works fine in connections.json
This works fine: “connection”: { “id”: “/subscriptions/@appsetting(‘AzSubscription’)/resourceGroups/@appsetting(‘AzResourceGroup’)/providers/Microsoft.Web/connections/azuredatafactory” },
While referencing subscription as @{appsetting(‘AzSubscription’)} doesn’t work.
@Sven5, Sorry for the delay in getting back on this. Currently we have an issue with transitive reference of app settings in Parameters. The product group is working on the fix. As of now, the template doesn’t work if,
We would update this thread once it is fixed. Meanwhile please check if the app setting can be directly used in the template for this requirement.