resource/aws_api_gateway_usage_plan_key: Support resource import

[DrFaust92]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Relates #558

Release note for CHANGELOG:

resource/aws_api_gateway_usage_plan_key: Support resource import 

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAWSAPIGatewayUsagePlanKey_'
--- PASS: TestAccAWSAPIGatewayUsagePlanKey_basic (163.66s)
--- PASS: TestAccAWSAPIGatewayUsagePlanKey_disappears (87.32s)
...

[bflad]

Thanks for submitting this, @DrFaust92 -- the implementation here is off to a good start. 😄 Rather than burdening operators to provide the key type during import, it looks like we should be properly performing drift detection of the attribute by setting it in the Terraform state in the Read function. This will remove the import ID requirement. Please reach out if you have any questions or do not have time to implement the feedback.

[DrFaust92]

--- PASS: TestAccAWSAPIGatewayUsagePlanKey_basic (188.10s)
--- PASS: TestAccAWSAPIGatewayUsagePlanKey_disappears (97.07s)

[bflad]

Looks good, thanks @DrFaust92! 🚀

Output from acceptance testing:

--- PASS: TestAccAWSAPIGatewayUsagePlanKey_disappears (21.37s)
--- PASS: TestAccAWSAPIGatewayUsagePlanKey_basic (106.97s)

[ghost]

This has been released in version 2.44.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!

[ghost]

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!