Added documentation for granular API groups feature in NGINX One

[kamalchaturvedi]

Proposed changes

Write a clear and concise description that helps reviewers understand the purpose and impact of your changes. Use the
following format:

Problem: Added changelog entry for already existing documentation for granular API groups in NGINX one.

Solution: N/A

Testing: Describe any testing that you did.

Please focus on (optional): If you any specific areas where you would like reviewers to focus their attention or provide
specific feedback, add them here.

If this PR addresses an issue on GitHub, ensure that you link to it here:

Closes #ISSUE

Checklist

Before merging a pull request, run through this checklist and mark each as complete.

• I have read the contributing guidelines
• I have signed the F5 Contributor License Agreement (CLA)
• I have rebased my branch onto main
• I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
• I have ensured that the commit messages adhere to Conventional Commits
• I have ensured that documentation content adheres to the style guide
• If the change involves potentially sensitive changes¹, I have assessed the possible impact
• If applicable, I have added tests that prove my fix is effective or that my feature works
• I have ensured that existing tests pass after adding my changes
• If applicable, I have updated README.md and CHANGELOG.md

Footnotes

1. Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩

[github-actions]

🎉 Thank you for your contribution! It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the F5 CLA and reply on a new comment with the following text to agree:

---

I have hereby read the F5 CLA and agree to its terms

---

1 out of 2 committers have signed the CLA.
✅ (mjang)[https://github.com/mjang]
❌ @kamal Chaturvedi
Kamal Chaturvedi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[kamalchaturvedi]

I have hereby read the F5 CLA and agree to its terms

[jasonclopper]

@kamalchaturvedi this references Namespace updates as well, Didn't think that was ready yet?

[kamalchaturvedi]

@kamalchaturvedi this references Namespace updates as well, Didn't think that was ready yet?

Those are XC namespaces, as referred to in the intro section of this page: https://docs.nginx.com/nginx-one/rbac/rbac-api/

You can associate these roles with specific namespaces, to help facilitate the principle of least privilege across your tenant.

Would adding a note regarding N1 support for namespaces coming soon help with this ? I wanted to ensure we give user the knowledge of how namespaces can help them segregate these permissions.

Otherwise, i am fine removing this line if it causes confusion.

[mjang]

Thanks for the PR, @kamalchaturvedi !

TLDR: I've tried to retain the essential info, while making the content easier to read. I also think that it's better to link to https://docs.nginx.com/nginx-one/rbac/rbac-api/.

[mjang]

Hi @kamalchaturvedi

• GitHub gave us a misleading error message (copied below). Of course you're a GitHub user, you have an account!
• The error seems to be related to https://docs.github.com/en/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user
  • Can you use step 4 of this process and check the email address connected to your GitHub account?

Inote: if this doesn't work, I have privileges to override and merge this PR.)

---

Kamal Chaturvedi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[jasonclopper]

I think Mike's changes are good.

[mjang]

Based on @jasonclopper 's approval, I'll merge my changes and approve and merge.