docs(waf): remove unimplemented Unwanted Access and Identified Attack flags - #2327
Merged
bruno-andrade-azion merged 1 commit intoSep 2, 2026
Merged
Conversation
… flags Engineering never implemented these two WAF threat families in the product, but they were still documented in the Main Settings threat table, the CLI config schema, and an API request example, across both locales. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
marcus-souza-azion
approved these changes
Sep 1, 2026
artur-rossa-azion
approved these changes
Sep 2, 2026
artur-rossa-azion
left a comment
artur-rossa-azion
left a comment
Contributor
There was a problem hiding this comment.
As long as the product still have visible and configurable options taken off by the changes in the API v4 and Console, it seems to be a product bug missalignment, and not just a documentation bug, by definition.
As the bug is recognized by Eng, confirmed by @bruno-andrade-azion), it's OK to go ahead, but is critical to confirm that the options mentioned were removed afterwise, to avoid sync problems between what users see in the cli/API/Console and what docs say about it.
bruno-andrade-azion
deleted the
docs/update-unwanted-acess-identified-attack
branch
September 2, 2026 13:12
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Related issue: none
Pages affected:
/en/documentation/products/secure/firewall/web-application-firewall/andpt-brequivalent/en/documentation/products/secure/firewall/web-application-firewall/rules-set/andpt-brequivalent/en/documentation/products/devtools/cli/azion-cli/config/azion-config-js/andpt-brequivalent/en/documentation/products/guides/secure/create-waf-rule-set/andpt-brequivalentEngineering never implemented the Unwanted Access and Identified Attack WAF threat families in the product, but they were still documented in the Main Settings threat table, the CLI/SDK config schema, and a sample API request payload — in both
enandpt-br. This PR removes every reference to keep the docs accurate.Type of change
feat)fix) — typo, broken link, wrong informationdocs) — rewrite, expansion, upkeepi18n)refactor/chore) — reviewed by UXE, no content mixed inAuthor checklist
type(scope): summary(see GOVERNANCE.md §4)title,description,meta_tags,namespace,permalink,last_reviewedpt-brupdated in this PR or follow-upi18nissue createdpnpm build:local(build + frontmatter check) without errors — attempted locally butastro buildran out of memory (OOM) in this environment, unrelated to the content change; no build errors were observed before the OOM