-
Notifications
You must be signed in to change notification settings - Fork 193
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 additional reasoning/requirements and suggestion for use to ES privileges #4197
Conversation
CC @romansmirnov for final review 👍 |
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.
Content-wise it looks good, that's basically what I have summarized at some point in Slack. Just added two questions.
- `manage_index_templates` to create and manage index schema on start up, if they don't already exist in Elasticsearch. | ||
- _Optional_ `manage_ilm` - required only when ILM is enabled | ||
- `monitor` - Required to check the Elasticsearch cluster health. This privilege provides read-only cluster operations permissions. | ||
- `manage_index_templates` - Creates the necessary index templates when Operate is started for the first time, or when updating to a newer version of Camunda 8. Once the index templates are created, you can stop Operate, remove this privilege, and then start Operate again. |
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.
❓ It explicitly mentions Operate, what about Tasklist (and Optimize)?
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've gone ahead and updated the file in /docs with a change to reference Operate, Tasklist, and Optimize (instead of only Operate). If this looks good I'll update it in the other files. 👍
- `manage_index_templates` - See [cluster privileges](#cluster-privileges). | ||
- `manage_ilm` - _Required when index lifecycle management (ILM) is enabled._ See [cluster privileges](#cluster-privileges). | ||
|
||
These privileges can be granted temporarily during an upgrade: |
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.
❓ Just for context, why are we documenting this? If I remember correctly, I summarized that in the context of a customer 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.
I don't have context for the original ask, only the summary. Can you specify if these permissions should be removed, and if so, which ones in particular?
8be2870
👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉 You can read more about the versioning within our docs in our documentation guidelines. |
axiosRef.defaults.headers[ | ||
"Authorization" | ||
] = `Bearer ${credentials.access_token}`; |
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.
[prettier] reported by reviewdog 🐶
axiosRef.defaults.headers[ | |
"Authorization" | |
] = `Bearer ${credentials.access_token}`; | |
axiosRef.defaults.headers["Authorization"] = | |
`Bearer ${credentials.access_token}`; |
axiosRef.defaults.headers[ | ||
"Authorization" | ||
] = `Bearer ${credentials.access_token}`; |
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.
[prettier] reported by reviewdog 🐶
axiosRef.defaults.headers[ | |
"Authorization" | |
] = `Bearer ${credentials.access_token}`; | |
axiosRef.defaults.headers["Authorization"] = | |
`Bearer ${credentials.access_token}`; |
axiosRef.defaults.headers[ | ||
"Authorization" | ||
] = `Bearer ${credentials.access_token}`; |
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.
[prettier] reported by reviewdog 🐶
axiosRef.defaults.headers[ | |
"Authorization" | |
] = `Bearer ${credentials.access_token}`; | |
axiosRef.defaults.headers["Authorization"] = | |
`Bearer ${credentials.access_token}`; |
axiosRef.defaults.headers[ | ||
"Authorization" | ||
] = `Bearer ${credentials.access_token}`; |
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.
[prettier] reported by reviewdog 🐶
axiosRef.defaults.headers[ | |
"Authorization" | |
] = `Bearer ${credentials.access_token}`; | |
axiosRef.defaults.headers["Authorization"] = | |
`Bearer ${credentials.access_token}`; |
axiosRef.defaults.headers[ | ||
"Authorization" | ||
] = `Bearer ${credentials.access_token}`; |
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.
[prettier] reported by reviewdog 🐶
axiosRef.defaults.headers[ | |
"Authorization" | |
] = `Bearer ${credentials.access_token}`; | |
axiosRef.defaults.headers["Authorization"] = | |
`Bearer ${credentials.access_token}`; |
I can't seem to resolve git thinking these tasklist files need to be added - closing to bring up to date and continue in #4704 |
Description
Closes #3355
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).