You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue 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 issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Importing an aws_lambda_alias will set function_name to ARN. However this does not work together with aws_lambda_provisioned_concurrency_config. As per the specified ticket.
Hi @terlar 👋 Thank you for submitting this. This import behavior was fixed with Version 3 of the Terraform AWS Provider since we consider changes like this to be breaking. Once upgraded, this automatic switch from name to ARN should no longer be an issue during import. 👍
Oh, what are the odds, sorry, should have checked that a new version was released, I just installed the latest one the other week, so wasn't aware of this. Thank you for fixing it!
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform v0.12.28
AWS Provider v2.70.0
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
terraform state rm aws_lambda_alias.test_lambda_alias
terraform import aws_lambda_alias.test_lambda_alias lambda_function_name/my_alias
References
Importing an aws_lambda_alias will set function_name to ARN. However this does not work together with
aws_lambda_provisioned_concurrency_config
. As per the specified ticket.The text was updated successfully, but these errors were encountered: