-
Notifications
You must be signed in to change notification settings - Fork 9.8k
Closed
Closed
Copy link
Labels
bugAddresses a defect in current functionality.Addresses a defect in current functionality.regressionPertains to a degraded workflow resulting from an upstream patch or internal enhancement.Pertains to a degraded workflow resulting from an upstream patch or internal enhancement.resource-identityPertains to resource identity.Pertains to resource identity.service/s3Issues and PRs that pertain to the s3 service.Issues and PRs that pertain to the s3 service.
Milestone
Description
Terraform and AWS Provider Version
Provider v6.14.0 on multiple platforms
Affected Resource(s) or Data Source(s)
Observed on aws_s3_object
, but other resources could also be affected by this (seeing the report for Lambda in #44361)
Expected Behavior
Provider should return cleanly after applying changes to aws_s3_object
like it does with provider 6.13.0.
Actual Behavior
The S3 object is uploaded, but the apply fail with the error:
aws_s3_object.test: Modifying... [id=test]
╷
│ Error: Missing Resource Identity After Update: The Terraform provider unexpectedly returned no resource identity after having no errors in the resource update. This is always a problem with the provider and should be reported to the provider developer
│
│ with aws_s3_object.test,
Relevant Error/Panic Output
Error: Missing Resource Identity After Update: The Terraform provider unexpectedly returned no resource identity after having no errors in the resource update. This is always a problem with the provider and should be reported to the provider developer
Sample Terraform Configuration
Click to expand configuration
resource "aws_s3_object" "test" {
key = "test"
bucket = aws_s3_bucket.test_bucket.id
content = "foobar"
etag = md5("foobar")
}
Steps to Reproduce
- Create an S3 object with
aws_s3_object
and provider 6.14.0 and watchterraform apply
fail with the error above - When running
terraform plan
again confirm no changes - Verify the object was indeed uploaded to S3 in step 1
- Downgrade to provider 6.13.0, change the file contents and see
terraform apply
upload successfully without any errors
Debug Logging
Click to expand log output
GenAI / LLM Assisted Development
n/a
Important Facts and References
No response
Would you like to implement a fix?
No
arkbriar, jakub-olczyk, thorsmann, bo4arov, tekiflo and 105 more
Metadata
Metadata
Assignees
Labels
bugAddresses a defect in current functionality.Addresses a defect in current functionality.regressionPertains to a degraded workflow resulting from an upstream patch or internal enhancement.Pertains to a degraded workflow resulting from an upstream patch or internal enhancement.resource-identityPertains to resource identity.Pertains to resource identity.service/s3Issues and PRs that pertain to the s3 service.Issues and PRs that pertain to the s3 service.