-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
aws_s3_bucket: During terraform import - ACL is populated with "null" in tfstate, and terraform apply defaults to acl=private #17791
Comments
irrespective of
# skipped ..
grant {
permissions = ["READ_ACP", "WRITE"]
type = "Group"
uri = "http://acs.amazonaws.com/groups/s3/LogDelivery"
}
grant {
permissions = ["READ_ACP"]
type = "Group"
uri = "http://acs.amazonaws.com/groups/global/AllUsers"
}
grant {
id = "someid"
permissions = ["FULL_CONTROL"]
type = "CanonicalUser"
}
# other details skipped for brevity
// skipped..
{
"schema_version": 0,
"attributes": {
"acceleration_status": "",
"acl": "private",
No changes. Infrastructure is up-to-date.
This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed. |
I ran into this bug as well and had to manually edit the state file. This should definitely be addressed. |
This looks like a duplicate of #6193 |
I have similar issue but always populated with
When importing the bucket , doing -target plan |
To get around this, I've added the below so that Terraform ignores the missing acl & force_destory, this saves having to mess around with the state file.
Interestingly a terraform state show doesn't list either of these. |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Note - This only occurs while
importing
S3 bucketDebug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
bucket.tf
terraform apply
The text was updated successfully, but these errors were encountered: