#8506 ability to import an existing lambda alias to terraform state

[richardjennings]

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" comments, they generate extra noise for pull request followers and do not help prioritize the request

Fixes #8506

Release note for CHANGELOG:

Import of existing lambda aliases to terraform state

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAWSLambdaAlias_basic'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./... -v -parallel 20 -run=TestAccAWSLambdaAlias_basic -timeout 120m
?       github.com/terraform-providers/terraform-provider-aws   [no test files]
=== RUN   TestAccAWSLambdaAlias_basic
=== PAUSE TestAccAWSLambdaAlias_basic
=== CONT  TestAccAWSLambdaAlias_basic
--- PASS: TestAccAWSLambdaAlias_basic (45.47s)
PASS
ok      github.com/terraform-providers/terraform-provider-aws/aws       45.518s

[bflad]

LGTM, thanks so much, @richardjennings! 🚀

Output from acceptance testing:

--- PASS: TestAccAWSLambdaAlias_basic (34.51s)
--- PASS: TestAccAWSLambdaAlias_nameupdate (40.00s)
--- PASS: TestAccAWSLambdaAlias_routingconfig (45.76s)

[bflad]

Typically d.SetId() should only be called during Create and Importer State functions, however this is understandably a little more nuanced here since if we followed that rule here we would need the entire alias ARN passed into terraform import or to make an additional API call in the import function which is less than ideal. I'm okay with merging this as-is for now to get this functionality in. 👍

[bflad]

This has been released in version 2.10.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[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!