[d/aws_lambda_function] Remove default qualifier #5812
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this pull request:
aws_lambda_function
data source to makearn
property consistent.I spent a few hours trying to debug a problem until I realized that the
aws_lambda_function
data source was appending:$LATEST
to the arn.Intuitively,
aws_lambda_function.lambda.arn
anddata.aws_lambda_function.lambda.arn
would return the same value.But this is required at the moment:
In my use case, I was trying to use the data source together with
aws_cloudwatch_log_subscription_filter
before I realized that mydestination_arn
had:$LATEST
appended. Addingqualifier=""
solved it.I have tried to see what difference
$LATEST
does, but I think only the arn changes. I have compared the output fromaws lambda get-function --function-name test-lambda
andaws lambda get-function --function-name test-lambda --qualifier '$LATEST'
and onlyFunctionArn
changes. I have not been able to otherwise identify any reason for the default value.Thank you!!
Output from acceptance testing:
(by the way, is there an easy way to run a list of acceptance tests? I tried adding multiple
-run
but it didn't work)