feat: extend support for rate based statement rules

[GuusDeGraeve]

what

• Adds support for scope_down_statement (including and statements) in rate_based_statement_rules
• Adds support for custom_response in rate_based_statement_rules block action
• Adds support for evaluation_window_sec in rate_based_statement_rules

why

• There was no way to set rate limiting rules for specific hostnames, paths or http methods
• There was no way to set custom responses for rate limiting rules when requests are blocked
• There was no way to set the evaluation window for rate limit measuring

references

closes #63

[osterman]

This should be added to the description

[osterman]

/terratest

[aknysh]

@GuusDeGraeve the PR looks good, thank you.

Some questions about this code

 for_each = length(lookup(scope_down_statement.value, "and", [])) > 0 ? [scope_down_statement.value.and] : []
                  content {
                    dynamic "statement" {
                      for_each = and_statement.value

Looks like scope_down_statement.value.and should be a list b/c you check its length.
But then you put it into another list in [scope_down_statement.value.and].
Should it be just ? scope_down_statement.value.and : [] ?

[GuusDeGraeve]

Hi @aknysh, yes that is correct, the reason is because the add statement is a list of multiple statements. Which we loop over within the next dynamic block dynamic "statement" {.

I know it looks quite confusing when reading the code, but it is definitely on purpose.

[aknysh]

@GuusDeGraeve thanks for the PR, please see comments

[mergify]

💥 This pull request now has conflicts. Could you fix it @GuusDeGraeve? 🙏

[mergify]

This PR was closed due to inactivity and merge conflicts. 😭
Please resolve the conflicts and reopen if necessary.