This repository has been archived by the owner on Feb 1, 2024. It is now read-only.

Make the "negated" key for the WAF rules optional #5

Open

danvaida opened this issue May 4, 2020 · 0 comments

Labels

danvaida commented May 4, 2020 •

edited

Loading

As the name suggests, the user should not be forced to explicitly set a value for an unused option.

We can use another local variable to manipulate the data structure using an inner loop.
Possibly enhancing this construct:

negated = length(each.value.byte_match_tuples) > 0 ? try(each.value.byte_match_tuples[0].negate, "false") : null

Change was introduced with PR #4

danvaida added the enhancement label

danvaida linked a pull request

that will close this issue

OPS-0 Adding negated property as variable #4

Merged

danvaida removed a link to a pull request

OPS-0 Adding negated property as variable #4

Merged

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.