Fix: Incorrect AWS Lambda Qualifier Regexp #11383
Conversation
Type of change: =============== - Bug fix What changed? ... and Why: ========================== The regexp is currently set to: `pattern := `^[a-zA-Z0-9$_]+$` The AWS docs state that qualifer names must conform to the following regexp: `Pattern: (|[a-zA-Z0-9$_-]+)` As you can see, the current regexp in Terraform is missing the `-` at the end. This addresses that. How has it been tested? ======================= Added a few test cases to the existing spec for `AwsLambdaQualifier` validation.
|
Hey @brad-larson – can you clarify for me what resources this impacts, and the documentation you're referencing? I'm looking at the API docs here: I'm not seeing the trading |
|
@catsby This impacts the Basically, the qualifier == the alias name, so if an alias name can contain |
|
AH ok, thanks! |
|
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. |
ghost
locked and limited conversation to collaborators
Type of change:
What changed? ... and Why:
The regexp is currently set to:
pattern := ^[a-zA-Z0-9$_]+$The AWS docs state that qualifer names must conform to the following
regexp:
Pattern: (|[a-zA-Z0-9$_-]+)As you can see, the current regexp in Terraform is missing the
-atthe end.
This addresses that.
How has it been tested?
Added a few test cases to the existing spec for
AwsLambdaQualifiervalidation.