-
Notifications
You must be signed in to change notification settings - Fork 1.2k
initial documentation for preview mode permissions #28842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
initial documentation for preview mode permissions #28842
Conversation
Preview links (active after the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small optional suggestions here - looks great!
Co-authored-by: Janine Chan <[email protected]>
Co-authored-by: Janine Chan <[email protected]>
Co-authored-by: Janine Chan <[email protected]>
make role and permission top level headings |
….com:DataDog/documentation into matthew.bilyeu/ACCESS-3350/preview-mode-docs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
What does this PR do? What is the motivation?
On AAA Core Access we are introducing a new state for permisisons called "Preview Mode". In preview mode a permission will be visible but not enforced. This gives administrators with custom roles the ability to opt in to certain new permissions before losing access to resources that were previously unrestricted.
This change adds a brief section to the public permissions documentation so that we can reference it in release notes, product links, etc.
Here's rendered preview
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes
cc @DataDog/aaa-core-access