I have worked in the industry for more than 10 years, as a developer and cloud architect in the UK. Solution architect professionally and a functional programming hobbyist.
I agree, Azure state drifting from your state file was a challenge for me, too.
Pulumi by default does not refresh the state, I am not sure I'm onboard with the default behaviour, but that causes less pain in that case as you only apply what you intentionally changed in code.
Usually, drifting happens when Azure Policy forces configuration, on that front I would probably enforce policies all in code as much as possible and lock resources to avoid external interference and set up alerts on configuration changed by users that are not the deployment principals.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thank you, Carlos.
I agree, Azure state drifting from your state file was a challenge for me, too.
Pulumi by default does not refresh the state, I am not sure I'm onboard with the default behaviour, but that causes less pain in that case as you only apply what you intentionally changed in code.
Usually, drifting happens when Azure Policy forces configuration, on that front I would probably enforce policies all in code as much as possible and lock resources to avoid external interference and set up alerts on configuration changed by users that are not the deployment principals.