-
Notifications
You must be signed in to change notification settings - Fork 2
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
Pulumi preview and up incorrectly says that it will change / is changing a service #648
Comments
FYI I have also tried to run |
Hi @JiriKovar, thank you for reporting this. We do have a category of bugs involving spurious diffs, and we understand they're confusing an unwieldy for our users. Some of these bugs stem from the pulumi-terraform bridge rather than an individual provider. In fact, we're currently working on improved diffing logic in the bridge. Even though they may have different causes, we'd love it if you could send us a sample program with such an unexplained diff. |
Hi, interresting is that we used to manage these Fastly services via Terraform until recently and with Terraform, we werent having these issues. The service in mention does not use any logging and the service itself is as simple as mentioned in the aforementioned code. I will try to come up with a minimal repro when I have a few moments to spare, but I have a couple of questions that could help me with that:
Thank you very much! |
Hi @JiriKovar -
It is possible; it is also possible that
it is helpful to know that you do not see this issue in Terraform. There are some significant differences between the way Pulumi creates a diff preview and the way Terraform does, and you may be tripping over some of them. This leads me to believe this is almost certainly a bug on our end with Diff. Please update here for a repro once you have it. In the meantime... I don't think we've addressed anything quite like this, but the team has put in a lot of work on Diff in the bridge in the last several weeks. I've triggered a patch release of this provider for you to try out. Once https://github.com/pulumi/pulumi-fastly/actions/runs/11674513405 is done building, try |
Hello @guineveresaenger, Unfortunatelly the patch And even worse, I was unable to come up with a reliable minimal repro. Parallel to that I was tryting to remove some parts of the affected service and I have noticed that whenever I remove WAF from an affected service, it fixed the issue, until I put the WAF back. But at the same time, not all services that use WAF are affected (which is why I dont have a reliable minimal repro yet). Another little piece of information is that when I create the Fastly Service with WAF, everything is OK (
This list that it is indeed caused by something around either WAF, or dynamic snippets. Based on that I'm thinking it might be the best option to move this conversation to the slack / Fastly support ticket, where we could safely share customer IDs and Fastly service IDs so that you can possibly look at the differences between the affected and unaffected services. Is that OK with you? |
I finally have a repro:
|
Hi @JiriKovar - thank you so much for your perseverance here in chasing down a repro for us. A couple points:
We'll take a look at the repro and see what's going on here as well. |
I'm running on Windows, so I presume the exact command you had in mind is this: When I tried that on an empty stack, the first
When I followed by running: |
Describe what happened
Hello,
In case of some of our service, the
pulumi preview
andpulumi up
commands shows that it will do "something" with a service (the service root is flagged with~
, prints details of the service, but in the details, nothing is flagged to be changed (no line starts with~/-/+
).In case of pulumi up, it says that its updating the services, the service is listed in the number of the updated services, but at the end of the day, it does nothing at all = not even a new version of the fastly service is created, which shows that at the runtime the Pulumi detects that there is no change - version management requires extra requests AFAIK and its not running even these requests. Even so, the next round of
pulumi preview
andpulumi up
shows the same results.Have you ever observed the same behaviour? Do you have any idea what could be the cause? In case of some of the types of our Fastly services, it happens only in certain configuration (for QA configurations some objects like ACLs or WAF are missing), in some of them it doesn't happen (even though they have ACLs and WAF), in some of them it happens consistently no matter the configuration.
This has been bothering us for quite a while, we had a couple of theories, but none of them proved to be right - it could be some handling of whitespaces, or whatnot. I'm reporting it as a bug, since the logs and the actual behaviour does not match, but at the same time I'm asking for assistance, because I cannot pinpoint the cause and give you a reasonable repro.
Sample program
Log output
Affected Resource(s)
No response
Output of
pulumi about
Additional context
No response
Contributing
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: