-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
4.2 - Docs: Workflow Beta #3155
Conversation
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.
Points that came up during the final review of #3131 and should probably be documented:
-
The
options.max_session_ttl
field of the requested role (dba
in your examples) provides an upper-limit on how long the access-request will be valid. If, for example, we wanted to ensure thatcontractor
would need to re-requestdba
every hour, setting theoptions.max_session_ttl
field ofdba
to 1 hour would be the correct way to do this. -
Granting a role with administrative abilities could allow a user to permanently upgrade their privileges (e.g. if
contractor
was grantedadmin
for some reason). This isn't particularly surprising, but it should be mentioned explicitly. Thedeny.request
block can help mitigate the risk of doing this by accident.
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.
Sorry, I saw this late - some spelling/grammar nits.
I can re-add them on the final PR review if needed.
Thanks Gus, I've gone ahead and fixed these. |
This PR has been opened against a new
4.2-base
branch to make reviewing easier. It outlines the new features for Workflows.