-
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 refresh does not detect an external change in the VCL Service name and that it has been deactivated. #629
Comments
Hi @JiriKovar - thank you for filing this issue. We're sorry you're having trouble. It is possible that you are running into this upstream behavior which occurs when a Service is deactivated outside of Pulumi/Terraform. It appears the provider does not actually detect these changes and carries on as before. The suggestion in that issue is to run I'm not sure what to tell you about the If you continue to get stuck here, could you please provide us with a minimally complete repro of this behavior, including step-by-step instructions to mirror the events in the Fastly console? |
thanks for looking into this. We are actually migrating from the Terraform to the Pulumi and please know that we have not faced this issue in the Terraform. Also, we have attempted to run the As for the As for the minimal repro, I believe that I wont be much of a help here - you need to specify only a name and a single domain to the ServiceVcl configuration and the rest is to connect the provider to a fastly account (I sadly cannot give you an access to our account) and then causing a drift in the Fastly once its created. So, here is the best I can give you:
|
Hi @JiriKovar - thank you for your response. We do have a Fastly test account, so if you could please clarify - we should see this behavior when:
Did you activate the Service manually before importing it? Is that something you could give a try? Could you also elaborate on
Please do let us know if you can report anything new here. |
Hi, yes, that list of steps is sufficient to reproduce the issue with the name. Whether the service is manually activated or not does not matter in case of the service name drift detection.
Not really - this is the case for the service that has been imported and managed by pulumi for several versions. |
Hey @JiriKovar, the issue does not reproduce for me.
Which version of the fastly provider are you using? Can you please try updating that to the latest version and retrying? |
Describe what happened
We have a several Fastly VCL services managed by ServiceVcl definitions that are already in the Pulumi stack (everything is up and running for some time).
A service name was changed outside of the Pulumi automation and it was deactivated due to reasons unrelated to this issue.
We wanted to rollback these changes with Pulumi, but the next pulumi up command with refresh flag did not notice any of these changes. The specific command is as follows:
pulumi up --refresh --yes --skip-preview
The same behaviour was also observed with the command
pulumi preview --refresh
= no changes detected.Then we have decided to test that the overall solution is working by manually creating a new version of the VCL Service through the Fastly UI, deleting a random part of the definition (it was an http header), activating it and running the aforementioned command again. At that point, it detected the missing part, added it back and activated the service, however the change in the name of the service has remained undetected and therefor was still not fixed.
Sample program
Log output
No response
Affected Resource(s)
No response
Output of
pulumi about
CLI
Version 3.131.0
Go Version go1.23.0
Go Compiler gc
Plugins
KIND NAME VERSION
language nodejs unknown
Host
OS Microsoft Windows 11 Enterprise
Version 10.0.22631 Build 22631
Arch x86_64
This project is written in nodejs: executable='C:\Program Files\nodejs\node.exe' version='v20.17.0'
TYPE URN
pulumi:providers:fastly urn:pulumi:fb94b::on_demand_client::pulumi:providers:fastly::default_8_11_0
fastly:index/serviceVcl:ServiceVcl urn:pulumi:fb94b::on_demand_client::fastly:index/serviceVcl:ServiceVcl::fb94b-draft
fastly:index/serviceDictionaryItems:ServiceDictionaryItems urn:pulumi:fb94b::on_demand_client::fastly:index/serviceVcl:ServiceVcl$fastly:index/serviceDictionaryItems:ServiceDictionaryItems::allowed_CORS_domains_fb94b-draft
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: