-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_ami data source with a name_regex including ** causes terraform to crash #9608
Comments
Relevant chunk of the Panic output, for easier reference:
|
@paulte hi there! Thank you for getting in touch! I have added a pre-flight, so to speak, validation of the regular expression that is passed down via the |
Closed via #9622 |
@paulte hi there! Just to add for the record - the |
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. |
Low priority bug report. It looks like name_regex within aws_ami doesn't handle the regular expression of **
I'm not suggesting there's a use case where ** would be considered required / desirable, more that it would be preferable that it didn't crash terraform.
Terraform Version
Terraform v0.7.7
Affected Resource(s)
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Panic Output
https://gist.github.com/paulte/73d2709161842737aa6fd4810664e80b
Expected Behavior
The regular expression ** should be considered equivalent to * and not crash terraform
Actual Behavior
Terraform crash
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: