resource/aws_iam_access_key: Ensure Inactive status is properly configured during resource creation#17322
Conversation
…gured during resource creation Reference: #16818 Previously before code updates: ``` === CONT TestAccAWSAccessKey_Status resource_aws_iam_access_key_test.go:71: Step 1/3 error: Check failed: Check 2/2 error: aws_iam_access_key.a_key: Attribute 'status' expected "Inactive", got "Active" --- FAIL: TestAccAWSAccessKey_Status (5.97s) ``` Output from acceptance testing: ``` --- PASS: TestAccAWSAccessKey_basic (8.96s) --- PASS: TestAccAWSAccessKey_encrypted (9.13s) --- PASS: TestAccAWSAccessKey_Status (27.74s) ```
YakDriver
left a comment
There was a problem hiding this comment.
Great 🎉
GovCloud:
--- PASS: TestAccAWSAccessKey_encrypted (16.38s)
--- PASS: TestAccAWSAccessKey_basic (16.39s)
--- PASS: TestAccAWSAccessKey_Status (39.30s)
us-west-2:
--- PASS: TestAccAWSAccessKey_basic (8.98s)
--- PASS: TestAccAWSAccessKey_encrypted (9.54s)
--- PASS: TestAccAWSAccessKey_Status (23.74s)
|
Gah, I was trying so hard not to have the 3 |
|
This has been released in version 3.27.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
|
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. Thanks! |
Community Note
Closes #16818
Previously before code updates:
Output from acceptance testing: