https://pulumi.com logo
Title
b

bumpy-byte-21437

10/06/2020, 12:46 PM
is this correct behaviour?, since state is maintained right?
t

tall-librarian-49374

10/06/2020, 1:16 PM
Yes, this is expected, you should run
pulumi refresh
to see the difference with the actual account
b

bumpy-byte-21437

10/06/2020, 1:22 PM
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
t

tall-librarian-49374

10/06/2020, 1:30 PM
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.
b

bumpy-byte-21437

10/06/2020, 1:31 PM
ok should i do a refresh and then an apply to accomplish this?
t

tall-librarian-49374

10/06/2020, 1:32 PM
You can do
pulumi up --refresh
b

bumpy-byte-21437

10/06/2020, 1:40 PM
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"
it should be recreated i think right?
is this something that needs to be addressed or am i doing something wrong 😀
t

tall-librarian-49374

10/06/2020, 5:46 PM
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?
b

bumpy-byte-21437

10/06/2020, 5:56 PM
Yeah sure