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

I have plenty of other workarounds I could use (e.g. updating user data across the pets outside pulumi so it's always 'up to date') but since the user data is irrelevant after first boot I would rather just ignore the change.

There's a few relevant features:
• The _ignoreChanges_ opt.
• The _protect_ opt.
• Rework into separate projects.
The opts are documented here: <https://www.pulumi.com/docs/concepts/options/>

Since it's a pet resource, there's a strong argument for reworking into a separate project. Since it would (probably?) have a different lifecycle and would be udpated / deployed on different schedules, you would use a different project to manage this most easily.

But the two opts, especially in combination, will ensure that it does what you need.

oh, completely agreed this isn't the most optimal solution. ignoreChanges looks perfect, will jump on it.

and then tomorrow's problem can be handled tomorrow.