Skip to content

eja - eli-732 - amending WAF rule name as presumably AWS do exact matching#612

Merged
eddalmond1 merged 1 commit intomainfrom
feature/eja-eli-732-amend-WAF-rule
Mar 20, 2026
Merged

eja - eli-732 - amending WAF rule name as presumably AWS do exact matching#612
eddalmond1 merged 1 commit intomainfrom
feature/eja-eli-732-amend-WAF-rule

Conversation

@eddalmond1
Copy link
Copy Markdown
Collaborator

Description

Amending override rule name

Context

So that the rule is matched correctly and sets behaviour as 'count' for the agent no header rule.

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@eddalmond1
Copy link
Copy Markdown
Collaborator Author

Terraform plan looks to be picking up the change

@eddalmond1 eddalmond1 merged commit 803cea6 into main Mar 20, 2026
26 checks passed
@eddalmond1 eddalmond1 deleted the feature/eja-eli-732-amend-WAF-rule branch March 20, 2026 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants