Closed black-bryan closed 10 months ago
My first shot at this resulted in ingress being disabled. Ran out of time to do it again today. Most likely user error since others have had it work without issue. I'd say don't treat this as a blocker, if I identify whatever got me mixed up I'll just make the tweak. I'd say LGTM!
@scottisloud, my guess is the fact that the curl
command or Invoke-RestMethod -Uri
command are now pointing to the path where the .yaml will live when this is merged caused you the issue. Sorry I should have called this out as part of the review notes.
As it does not look like there are any "real" containers created in your Container App. You can test with curl https://raw.githubusercontent.com/1Password/scim-examples/solutions/bb/aca-yaml/beta/azure-container-apps/aca-op-scim-bridge.yaml --output aca-op-scim-bridge.yaml --silent
for and repeat the other command in step 9.
Overall improvements to the Azure Container App deployment guide.
yaml
deployment over theaz containerapp create
commands for separate containers.--enable-workload-profiles false
to theaz containerapp env create
command to accommodate the change made by Azure on December 5th version 2.55.0 in the AZ CLI tooling.