Closed hichamveo closed 2 years ago
@hichamveo - do you happen to know if the sku
property is necessary to create the resource? Often Export will return extraneous properties that are not required.
Don't see other way to specify the standard tier
I've tried going through the Portal experience to create a "Standard" logic app (https://portal.azure.com/#create/Microsoft.LogicApp, select "Review + Create", and then select "Download a template for automation").
The template generated for me (which has been authored by the LogicApps team) doesn't contain a sku
property. If I try to create a "Consumption" logic app, the template that the Portal generates is totally different - it instead gives me a resource of type Microsoft.Logic/workflows
, and no resource of type Microsoft.Web/sites
.
So it feels like sku
legitimately isn't accepted as a property on the Microsoft.Web/sites
resource, and that the type of the resource indicates whether it's a "Standard" or a "Consumption" plan. I think you could safely omit the sku
property in your sample.
Based on our conversation with @naveedaz, the sku of the website/logicapp is determined by the SKU of the underlying App Service Plan. The SKU for web/sites is read-only and the reason it is being exported is because export isn't aware that it is read-only and it shows up in the GET response. Does that help clarify?
Thanks a lot @alex-frankel & @anthony-c-martin , I'm now able to deploy my IPaaS infra with Bicep.
Bicep version v0.4.1008
Describe the bug Not able to create a LogicApps Standard via Bicep
To Reproduce Steps to reproduce the behavior: When adding Logic Apps standard resource, the sku property is not recognized :
ARM template from Azure portal :
Additional context
is there any sample to follow to provision a LogicApps Standard?