Change policy application approach for "XML Threat Protection for API Gateway"
Open
Nobody has claimed this yet.
API-M-4.1.0
API-M-Master
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
With the introduction of operational policies, previous approach of applying sequences is changed from APIM 4.1.0 onwards. This should be done using "Policies" view of an APIM publisher instead of using "Runtime" view.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the documentation for XML Threat Protection in APIM and review how the current APIM 4.1.0 guidance applies sequences. Update the instructions to use the publisher's Policies view rather than the Runtime view, then verify the surrounding operational-policy guidance is consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100