-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Docs Update: Graceful shutdown request needs X-Trino-User header #22593
Comments
cc @mosabua |
Sounds good. Did you want to supply a complete example here or send a PR @mgorbatenko ? |
@mosabua I don't have the CLA signed but something like this example should do 😄
|
X-Trino-User isn't the only requirement. The user must also have permissions to write "system information" (for a file-based access control example see #22589). Additionally if cluster is protected by authentication then the request must be authenticated too. |
I am a new potential contributor focused on documentation. Would it make sense for me to make this change and submit a pull request (as a training exercise of sorts)? |
@datasundae please do :) |
Does the @hashhar concern regarding "The user must also have permissions to write "system information" need to be addressed in the docs also? Would that just be a "Remember: The user must also have permissions to write "system information" statement? |
trinodb#22593 adding phrase -H X-Trino-User: authorizeduser to code"
OK I created a pull request. So far so good but I need to sign the CLA and it's not clear how I do that - expected a bot to direct me but didn't see anything. Will ask in the beginner Slack |
Nevermind CLA form came via email |
Not a huge deal, but the docs show this as an example api request for graceful shutdowns on worker nodes:
Without an
X-Trino-User
header, the request results in401 Unauthorized
.It'd be nice if the docs include the header so that future users know to add it.
I've outlined some of my learnings on the Trino slack here.
The text was updated successfully, but these errors were encountered: