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

Were these resources created from a Helm chart?  What is the resource type of the resource that saw the change you pasted above?  

This should not be related to the state file itself - but may be related to strings generated on the client machine and stored in the state file. 

Cc <@UBAJ7TD53> 

it just a part of it, for an example, a lot of the resorces changed, I just checked a few and that's where I saw the line ending difference

Here's the preview link which show this, I assume you can look at it: <https://app.pulumi.com/ncsibra/dev/previews/fdcaeb2f-a1b5-4302-a06a-476a0ee211ed>

I hope I didn't leave any uncommitted change, but I will check tomorrow at work

<@UDDF5MPU4> I actually can’t see this.

I agree with luke that it is conceivable that the component resource registers as changed, but I would find it quite odd if it caused the child resources to register as changed.

pulumi_state

I didn't left any uncommitted changes and after first look it's not clear what caused the change, an inline diff would be really helpful, instead of a deleted/added look :slightly_smiling_face:

Okay - yeah - looks like the primary issue is the yaml.ConfigGroup yaml property containing platform-dependent new lines.  <@UBAJ7TD53> want to open a bug in that?

I can’t quite tell if there are other similar issues in Pulumi-eks or other parts of the system as well here. Cc <@U84HBHXS8> 

<https://github.com/pulumi/pulumi-kubernetes/issues/254>