-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permenant diff #1386
Comments
I'm sorry this is not working as expected! There are some subtleties like pulumi/pulumi-aws#4336 where we're normalization logic is not quite complete, we've been working with the upstream provider (Terraform AWS provider) to get this to work better. Unfortunately to make progress on this our team needs a very specific self-contained repro. If you could provide this it would be greatly appreciated! |
Hi, sorry this took a while i had some things i needed to finish and i worked on this during the weekend i tried to mimic my current deployment without a ton of other extras but i was still able to reproduce it, details are in the readme @t0yv0 let me know if i can be of further hellp |
Thank you! |
Hey @aeweda, I wasn't able to trigger a perma-diff with the repro you provided. Is there any additional steps/setups needed to trigger this? |
@flostadler i just re tried it with a fresh stack / clone of the repo and it's still consistent, here's what i did
not sure why you can't reproduce it but it's pretty consistent, as i said this is the pascalcase vs camelcase issue. the perma diff is i'm assuming is related to the fact i have 60 different clusters in my workflow and that could be a factor, but if that pascal/camel issue was fixed i could focus on reproducing the other one as i believe they're somewhat separate just to clarify something as well, i said perma diff because on my repo it's always showing the pascal vs camel as changes even without changing anything unlike the bug-repro repo |
@flostadler i've also been doing some digging and the cloud formation schema linked on aws docs shows the json/yaml config in pascalcase, could it be a recent change or something that broke this? |
Ah ok @aeweda, yes I can reproduce the pascal case vs camel case issue now but not the perma-diff. Cloudformation uses pascal case (generally, not only for this resource), but we're integrating with the AWS APIs directly. I understand that it's hard to further debug the perma diff on your end with 60 different clusters. Let me know if you have any observations or a hunch what could trigger it, otherwise I'll first focus on getting the pascal case vs camel case diff issue resolved. |
Quick update from my end, I'm still working on finding the root cause for the capitalization issue but couldn't pin point it yet. I'll keep you posted with my findings |
What happened?
i'm facing an issue that's driving me a bit insane, everytime i do a preview or an update all my ecs clusters are marked as changed, specifically task definitions & container definition
i had this issue before but it was contained to container env vars and i was gonna fix it by implementing a deep sort however now it's global
the problem is persistent in ci,local
Example
Output of
pulumi about
Additional context
i checked on AWS itself and the task definition is stored as
camelCase
as it should be, idk why pulumi is comparing with a downstream ofPascalCase
also i tried switching to
pulumi-aws
instead ofawsx
yet the same problem persisted, i should also mention this problem did not happen 2 days agoContributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: