provider can't remove manually created CORS drift #7731
Assignees
Labels
Comments
|
@wyardley can you share the debug log? |
|
@edwardmedia I already "fixed" it in the original use case, but this is trivially reproducible (just verified, and ran with debug logs) resource "google_storage_bucket" "test-bucket" {
name = "tmpbucket12349"
}
[{"maxAgeSeconds": 3600, "method": ["GET", "POST", "PUT", "DELETE", "OPTIONS"], "origin": ["*"], "responseHeader": ["Content-Type", "access-control-allow-origin"]}]create the bucket and then I'm not posting the full debug output, because even with resource targeting, some other stuff from my state shows up, but here's the part that I think is relevant; if that's not enough, I think this is very easy to reproduce. [edit: I had initially reproed it with an older provider version, so updating the debug output here with the same thing, but from the latest provider] edit: also including the section where I'm trying to apply it, which I'm guessing you'd need too: |
|
I do see below change in the plan but the result of |
5 tasks
This was referenced Nov 20, 2020
|
Thanks @c2thorn @edwardmedia |
|
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 👉 hashibot-feedback@hashicorp.com. Thanks! |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm seeing an idempotency issue where, if CORS settings are altered outside of terraform, the provider can't bring the resource back into line.
Community Note
modular-magicianuser, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
google_storage_bucketTerraform Configuration Files
(slightly sanitized)
Debug Output
I can repro this if needed, but don't have it available.
Panic Output
Expected Behavior
Terraform reverts the drift and removes CORS settings
Actual Behavior
Terraform continues to try to apply the same changes on every run. example plan:
- cors { - max_age_seconds = 3600 -> null - method = [ - "GET", - "POST", - "PUT", - "DELETE", - "OPTIONS", ] -> null - origin = [ - "*", ] -> null - response_header = [ - "Content-Type", - "access-control-allow-origin", ] -> null }Steps to Reproduce
terraform applyImportant Factoids
References
The text was updated successfully, but these errors were encountered: