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

This project basically just sets up an Azure Container Registry, an App Registration, the Service Principal (plus password) and then failed on the RoleAssignment.

Anyone up for some comments on this one? For my personal case this thing is fixed by refreshing state and executing again with the correct permissions, but I assume this should fail differently. I’d like to support in this case but need to understand if there was a mistake / misunderstanding on my side or if this really should not happen like that.

Pulumi setup: using azure provider with a service principal that lacks the permission to perform `RoleAssignment`s (it was contributor only).

Pulumi program: creating an `AppRegistration`, `ServicePrincipal`, `ServicePrincipalPassword`, some other resource, here a `ContainerRegistry`. Trying to create a `RoleAssignment` for the ServicePrincipal results in an error, I was not able to find any resources on Azure, but the pulumi state had most of them listed.

So I’m wondering why the resources are listed in the state but don’t exist in Azure.