-
Notifications
You must be signed in to change notification settings - Fork 140
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
fastly_service_vcl.logging_bigquery always shows change #798
Comments
👋🏻 Hi @LevOlkha Can you provide (or some of) your Terraform configuration (i.e. your Fastly specific configuration such as your It would be useful to know what your state looks like for that particular resource block (e.g. It looks like from the log output that it's trying to update the logging resource block. Could you try running your TF_LOG=DEBUG FASTLY_DEBUG_MODE=true terraform apply Thanks. |
@Integralist I compared in logs file we can see ( I redacted parts)
and in
all and
what is interesting that if I create plan So it seems that values saved in state file are not the same as applied in plan |
Just as a data point, python/pythondotorg@1795b1f#diff-c4edee4039d22cfe2fd0d1ef214e7eba022aa85b29dd5677f4485f60e5b7a668 Similarly, when recently trying to enable NGWAF for PyPI we had to upgrade the Fastly TF provider from v1 to v5.16. https://github.com/pypi/infra/pull/172/files We now see in our plans that it also always now shows changed for The only commonality here is the ugpraded Fastly provider, I think. |
Same issue with I think I figured it out. API returns new line at the end on private key, while you're passing key with no new line at the end.
|
That was a red herring 🤦 , unfortunately.
I changed it so instead of
and that helped after 1 apply |
Terraform Version
Affected Fastly Terraform Resource(s)
Please list the affected resources, for example:
fastly_service_vcl
Terraform Configuration Files
Expected Behavior
when no change to configuration is made, no changes should be done for plan
Actual Behavior
logging_bigquery
is always reporting changeDebug Output (optional)
2024-01-02T11:43:20.075-0800 [DEBUG] provider.terraform-provider-fastly_v5.6.0: Creating clone of version (614) for updates: timestamp=2024-01-02T11:43:20.075-0800
2024-01-02T11:43:20.831-0800 [DEBUG] provider.terraform-provider-fastly_v5.6.0: Sleeping 7 seconds to allow Fastly Version to be available: timestamp=2024-01-02T11:43:20.831-0800
2024-01-02T11:43:27.834-0800 [DEBUG] provider.terraform-provider-fastly_v5.6.0: Update BigQuery Opts: fastly.UpdateBigQueryInput{AccountName:(*string)(nil), Dataset:(*string)(nil), Format:(*string)(nil), FormatVersion:(*int)(nil), Name:"BigQuery", NewName:(*string)(nil), Placement:(*string)(nil), ProjectID:(*string)(nil), ResponseCondition:(*string)(nil), SecretKey:(*string)(0xc0005a1130), ServiceID:"", ServiceVersion:615, Table:(*string)(nil), Template:(*string)(nil), User:(*string)(nil)}: timestamp=2024-01-02T11:43:27.834-0800
Steps to Reproduce
terraform apply
Important Factoids (optional)
Is there anything atypical about your account or set up that we should know?
The text was updated successfully, but these errors were encountered: