-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
WAF - 2 bugs since 0.9.6 - Optional fields accidentally now required #1107
Comments
…and xss detection rule creation to deal with a bug since 0.9.6 and present in 0.9.11 -- see here: hashicorp/terraform-provider-aws#1107
👍 for this. |
I've found the objects are still created when you leave out the 'data' field. |
Thanks @edify42 - do you have a quick snippit of that? I was going to use |
Closing as duplicate of #966 Full explanation in #966 (comment) |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Hi there,
Summary of the problem:
It looks like the OPTIONAL 'data' field in the AWS WAF "SQL Injection Match", and "XSS Match" is required to have a value that's not empty, even when the field is not required.
Terraform Version
Terraform v0.9.6
and
Terraform v0.9.11
Affected Resource(s)
aws_waf_sql_injection_match_set
aws_waf_xss_match_set
Terraform Configuration Files
There are two that have the same issue (optional field now required):
The other problem with the XSS is:
Expected Behavior
It should work because PER Amazon's docs (and Terraforms) the "data" field is completely optional:
https://www.terraform.io/docs/providers/aws/r/waf_sql_injection_match_set.html#data
and
https://www.terraform.io/docs/providers/aws/r/waf_xss_match_set.html#data
Actual Behavior
It failed with:
and
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
If you add the optional "data" field with "SOME-JUNK-VALUE" it works. As long as it's not an empty string. Again, this should not be required.
References
N/A
The text was updated successfully, but these errors were encountered: