fast-vr-604912/08/2022, 2:17 AM
clever-sunset-7658512/08/2022, 2:32 AM
property is not used. Essentially, all your container apps will run in the
for that environment. See https://github.com/microsoft/azure-container-apps/issues/374.
at the time. You said the same setup worked for you a few days ago, which provider version did you use then?
fast-vr-604912/08/2022, 6:21 PM
! This issue is presenting even from a complete rebuild of all the resources in the project, sadly. I can manually intervene and create the TXT record using the verification ID that the error response contains, so worst-case scenario, you can do that too, until the issue is resolved. This behaviour was working on Azure Native provider version
as of ~1 month ago
. I also noticed I'm out of date on that provider, trying again with
clever-sunset-7658512/08/2022, 6:45 PM
, I feel it might not be an issue with the provider or Pulumi. I think there was a Pulumi SDK bump with that version so any behavior changes should have affected your first time execution too. The Pulumi SDK that the provider depends upon was again bumped in the next patch version. So I am really curious if
fixes it for you.
fast-vr-604912/08/2022, 6:46 PM
clever-sunset-7658512/08/2022, 6:49 PM
I updated the issue report with this information too. I wonder if, in the meantime, I could wrap the Container App resource creation with a try-catch and grab the verification ID from the error message?Hmm I don't think you could do that. Even if it worked, you'd still have to re-run your infrastructure app because the creation of the container app would have failed. It will likely get a bit hacky after that.