Inconsistency in AWS Terraform provider with aws_lambda_function

[Sarah-E-Greene]

When using a data resource for aws_lambda_function, the qualified_arn comes back as:

arn:aws:lambda:us-east-1:1234:function:foo:$LATEST

But the non-data resource has a qualified_arn of:

arn:aws:lambda:us-east-1:1234:function:foo:5

Why is this different?

This breaks for us when using the data resource for a lambda with a cloudfront distribution, as it requires the qualified_arn to end with a number:

Error: error creating CloudFront Distribution: InvalidLambdaFunctionAssociation: The function ARN must reference a specific function version. (The ARN must end with the version number.)

Community Note

• 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

Terraform Version

0.12.19

Affected Resource(s)

• aws_lambda_function
• data.aws_lambda_function

Expected Behavior

Data resource for aws_lambda_function should have returned arn:aws:lambda:us-east-1:1234:function:foo:5, like the non-data resource.

Actual Behavior

Data resource for aws_lambda_function returned arn:aws:lambda:us-east-1:1234:function:foo:$LATEST

[justinretzolk]

Hey @SarahRiley 👋 Thank you for taking the time to file this issue. In reviewing the documentation, it seems as though the behavior may have changed, but I'm not not entirely sure which version of the AWS provider you were previously using, so it's difficult for me to say with certainty. With that in mind, given that there's been a number of AWS provider releases since you initially filed this, I wanted to follow up and see if you're still experiencing this behavior.

[Discipe]

This is still reproducable in Terraform 1.0.11 and aws provider 3.68.0

[breathingdust]

Hi all 👋 Just letting you know that this is issue is featured on this quarters roadmap. If a PR exists to close the issue a maintainer will review and either make changes directly, or work with the original author to get the contribution merged. If you have written a PR to resolve the issue please ensure the "Allow edits from maintainers" box is checked. Thanks for your patience and we are looking forward to getting this merged soon!

[ewbankkit]

Closed via #11195.

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.