Update Publisher REST API documentation to use "apim:api_publish" scope for LC based operations
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
Eg: In https://apim.docs.wso2.com/en/latest/reference/product-apis/publisher-apis/publisher-v2/publisher-v2/#operation/getAPISwagger
When the API is in PUBLISHED or DEPRECATED state: either one of the scopes are additionally required to update the APIs.
APIM 4.0.0
- apim:api_publish
- apim:admin
- apim:api_import_export
Above APIM 4.0.0
- All above can be used
- apim:api_manage
These needs to be reflected in API documentation.
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
Open the Publisher v2 getAPISwagger operation page linked in the issue and compare its LC-based operation scope requirements with the APIM 4.0.0 and later lists in the report. Update the documentation to reflect those version-specific scopes, then verify the operation page shows all listed alternatives.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100