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

is this correct behaviour?, since state is maintained right?

Yes, this is expected, you should run `pulumi refresh` to see the difference with the actual account

ok when i do a refresh i see the differences

how can i enforce the actual code while resources in azure are different

the declaritive code is enforced as truth in terraform for example, even when you do changes in the cloud

is the way of thinking different in pulumi

Terraform is the same story but they do refresh automatically before any apply. You can opt in to do the same in Pulumi, there is an option for that.

ok should i do a refresh and then an apply to accomplish this?

ok thanks, the weird thing is does detect the changes

but it doesn’t apply them.. i just says nothing changed

in this case i changed the lifecycle policy name in azure

when i delete the management policy it’s even worse

it then says: `error: Preview failed: autorest/azure: Service returned an error. Status=404 Code="ManagementPolicyNotFound" Message="No ManagementPolicy found for account dkotst351"`

is this something that needs to be addressed or am i doing something wrong :grinning:

I can’t say based on the message… If you think it’s not correct, could you please open an issue with the steps to reproduce?