[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)
Issue description
Deployment succeeds when not specifying platform in a container app's auth config. This causes a portal bug.
Steps to reproduce
Create a container app (through bicep)
Do not specify the platform configuration
Deployment should succeed
In portal, go to container app > settings > authentication. There will be a notification telling you to enable authentication on the container app, along with a call to action button. Clicking this will trigger an infinite deployment, opening developer console reveals that it can't find the platform attribute.
Expected behavior [What you expected to happen.]
An error should be thrown during deployment or at portal if platform is not required property.
Actual behavior [What actually happened.]
Portal does not expect platform attribute to not be present and causes error. Re-deploying with platform property solves issue
Screenshots
Additional context
bicep used, notice the .properties.platform in comment of the authConfig child resource:
This issue is a: (mark with an x)
Issue description
Deployment succeeds when not specifying platform in a container app's auth config. This causes a portal bug.
Steps to reproduce
Expected behavior [What you expected to happen.] An error should be thrown during deployment or at portal if platform is not required property.
Actual behavior [What actually happened.] Portal does not expect platform attribute to not be present and causes error. Re-deploying with platform property solves issue
Screenshots
Additional context
bicep used, notice the .properties.platform in comment of the authConfig child resource: