Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Update the Microsoft.Web/connections schema
See original GitHub issueAre there plans to publish an updated version of the Microsoft.Web/connections swagger? As far as I can tell, the current version is 2016-06-01.
When creating an API connection for a Logic App, there is a need to set the kind property to “V2” in order to get the connectionRuntimeUrl output property. The Bicep linter in VSCode produces a warning that kind and connectionRuntimeUrl are not defined in the resource definition.
If I’m understanding the process correctly, a schema update would resolve this issue. There are two open issues in the Azure Bicep repo on GitHub related to this:
- Azure/bicep/issues/3494
- Azure/bicep/issues/3512
Additionally, there doesn’t seem to be a published schema for Microsoft.Web/connections/accessPolicies. This makes the Bicep authoring experience in VSCode more challenging as the developer doesn’t know if what they’re writing is structurally correct.
acceessPolicies
connectionRuntimeUrl
AB#15956455
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@alexkarcher-msft @hartra344 Could you please provide an update to the schema release date? (And please re-open as it is still an issue)
This is on our roadmap for the next release of the Microsoft.Web definition. We have just updated the definition to include /workflows routes a few weeks ago and we are targeting to have the /connections schemas added by the end of the year.