-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Spurious Diff on quic_override attribute of google_compute_target_https_proxy #4859
Comments
@rileykarson I'm happy to PR this if you want, I appreciate you're probably pretty busy. Just wanted to confirm the issue before shooting from the hip as I'm not an expert on writing terraform modules. |
Can you try |
We've already worked around this and I don't want to revert that change and re-deploy to all our environments, so I can't verify that the change you're referencing fixes this issue. That said, I'm confident that it would, so unless you'd like input on verifying this fix I'm happy to close this issue and call it good. |
Thanks! I'll close this out, let us know if you run into it again for whatever reason. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
Terraform Version
Affected Resource(s)
google_compute_target_https_proxy
Terraform Configuration Files
Expected Behavior
quic_override
should be treated as a computed attribute when not set and left at its default value, "NONE".Actual Behavior
Steps to Reproduce
Have a target https proxy created before quic_override was introduced and then run
terraform apply
The text was updated successfully, but these errors were encountered: