Add two separate sections for apim vs apictl under "Defining a Backend Security Scheme" title
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
Currently, there is only single explanation without specifically mentioning to be used with apim or apictl.
It should be updated for both.
For example there should be two sections explaining for:
- Choreo Connect with apim
- Choreo Connect with standalone mode
Suggested Labels:
Suggested Assignees:
Affected Product Version:
4.0.0
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:
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 with the linked “Defining a Backend Security Scheme” documentation section and review its current explanation. Separate the guidance into sections for Choreo Connect with apim and Choreo Connect in standalone mode, with both usage paths clearly explained; the documentation should distinguish which instructions apply to each mode.
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
- 45/100