-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add docs for role.spec.allow.reason.mode #49363
base: master
Are you sure you want to change the base?
Conversation
This pull request is automatically being deployed by Amplify Hosting (learn more). |
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 but hold this off until after implementation is merged
resource allowed by "root-node-access" they will be required to provide a reason. This is true even | ||
if they are assigned to another role which allows requesting those roles/resources and doesn't have | ||
the reason mode set to "required". Or in other words, if there are multiple roles allowing | ||
requesting the same roles/search_as_roles with request mode set, "require" has a higher priority | ||
than "optional". |
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.
Nit: A little shorter and still carries the point across.
resource allowed by "root-node-access" they will be required to provide a reason. This is true even | |
if they are assigned to another role which allows requesting those roles/resources and doesn't have | |
the reason mode set to "required". Or in other words, if there are multiple roles allowing | |
requesting the same roles/search_as_roles with request mode set, "require" has a higher priority | |
than "optional". | |
resource allowed by "root-node-access" they will be required to provide a reason. If | |
a user's roleset includes multiple roles governing access requests to the same roles | |
and resources, "require" mode takes precedence. |
|
||
```yaml | ||
kind: role | ||
version: v6 |
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.
version: v6 | |
version: v7 |
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.
Should I change it in all examples in on this page?
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.
Yeah role v7 is the latest, we should prefer using it.
|Value|Meaning| | ||
|---|---| | ||
| `optional` | The default. The user does not need to provide a reason when making a request. | | ||
| `required` | The user must provide a reason when making a request. | |
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.
| `required` | The user must provide a reason when making a request. | | |
| `required` | The user must provide a non-empty reason when making a request. | |
🤖 Vercel preview here: https://docs-dtgn2ddrw-goteleport.vercel.app/docs |
## Reason mode | ||
|
||
Reason mode allows enforcing users to provide reason while making an Access Request. It only works | ||
in allow rules and is set with `allow.request.reason.mode`. |
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.
nit: "Reason mode" feels weird written out in english, maybe this is better
## Reason mode | |
Reason mode allows enforcing users to provide reason while making an Access Request. It only works | |
in allow rules and is set with `allow.request.reason.mode`. | |
## Requiring request reasons | |
The `allow.request.reason.mode` field controls whether a reason is required when users submit access requests. |
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.
I don't have a strong opinion here. @r0mant ?
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.
Nic's suggestion looks good to me.
cab0166
to
60382dd
Compare
🤖 Vercel preview here: https://docs-6ts77i7ro-goteleport.vercel.app/docs |
60382dd
to
d7fa1c2
Compare
|
||
If a user with "node-requester" role assigned makes an Access Request for "node-access" role or any | ||
resource allowed by "root-node-access" they will be required to provide a reason. If a user's | ||
roleset includes multiple roles governing access requests to the same roles and resources, |
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.
roleset includes multiple roles governing access requests to the same roles and resources, | |
roleset includes multiple roles governing Access Requests to the same roles and resources, |
We're capitalizing "Access Requests" across the docs. Not sure why it's not capitalized here but it is earlier in the paragraph.
🤖 Vercel preview here: https://docs-mwizanfer-goteleport.vercel.app/docs |
No description provided.