No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

G'day.  When running `pulumi up` to build &amp; deploy dotnet code that creates a few test `containerApp` instances (specifically, <https://www.pulumi.com/registry/packages/azure-native/api-docs/app/containerapp/#azure-native-app-containerapp|these>), the preview details show that it intends to update, but no real changes.  (first screenshot.  fields to be updated = yellow; no changes = white)

Also, for whatever reason, containerApp changes usually go 20+ minutes before eventually erroring out with the message "Error details:  Operation expired."  (2 screenshots).

Finally, despite the errors, the resources get created in Azure.  Seems like the 20-min timeouts stop pulumi from realizing that.  If there are legit errors in addition to the the timeouts that occur on previous runs, sometimes the resources get created, but not recorded to the pulumi stack.  (4th screenshot.)

Is this just me or has this behavior been witnessed by others?  Anyone see anything I could be doing differently?  What additional details would help?

From top of my head. I would check the revisions panel on the deployed apps and look at:
• Console logs to check if the containers are starting successfully
• Verify health checks and ingress port configurations are correct
• Check if container apps is able to pull the container from the registry. Have you set up permissions/credentials for that?