Azure / Azure/azure-rest-api-specs
[BUG] logicAppsAccessControlConfiguration missing on `Microsoft.Web/sites` for Logic App Standard
Nobody has claimed this yet.
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 6k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 432
Description
API Spec link
API Spec version
2024-04-01
Describe the bug
As described by arjunchiddarwar in 'Trigger workflows in Standard logic apps with Easy Auth', Logic App Standard can be configured not to accept SAS tokens for HTTP triggers using the following ARM.
"logicAppsAccessControlConfiguration": {
"triggers": {
"sasAuthenticationPolicy": {
"State": "Disabled"
}
}
}
Expected behavior
logicAppsAccessControlConfiguration is available as property on Microsoft.Web/sites
Actual behavior
logicAppsAccessControlConfiguration is not a known property on Microsoft.Web/sites. When deploying ARM/Bicep using the property the deployment succeeds and looking in the Azure Resource Explorer the property is set correctly.
Reproduction Steps
Used Bicep that works, but the logicAppsAccessControlConfigurationis not recognized as valid property. I have valided that this is not a Bicep issue, but that the property is also missing in this repo.
resource functionApp 'Microsoft.Web/sites@2024-04-01' = {
name: functionAppName
location: location
kind: 'functionapp,workflowapp'
properties: {
...,
logicAppsAccessControlConfiguration: {
triggers: {
sasAuthenticationPolicy: {
state: 'Disabled'
}
}
}
}
}
Environment
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with specification/web/resource-manager/Microsoft.Web/stable/2024-04-01/WebApps.json and inspect the Microsoft.Web/sites properties. Compare the schema with the ARM/Bicep example in the issue, then verify that logicAppsAccessControlConfiguration is accepted as a sites property and that the specification remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100