Create documentation for Multi Region APIM Deployment for both APIM 3.2.0 and 4.0.0
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
We do not have a document on $subject. It is a required patter for high availability. Therefore, it is essential that we have these.
Suggested Labels:
API-M-3.2.0
API-M-4.0.0
Priority/High
Suggested Assignees:
Affected Product Version:
All versions from 3.2.0 onwards
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
Start by locating the existing documentation structure for APIM 3.2.0 and 4.0.0 and any deployment or high-availability guidance. Define the missing multi-region deployment content for both versions, then verify that the resulting pages explain the required high-availability pattern.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100