[Sentinel One] - Fix Cannot execute ILM policy delete step #133793
Conversation
elasticsearchmachine
added
needs:triage
mohitjha-elastic
force-pushed
the
enhancement/sentinel_one-add_ilm_delete_index
branch
from
2fd1db5 to
e04c727
Compare
|
We would need this to be backported to at least |
… enhancement/sentinel_one-add_ilm_delete_index
…b.com:mohitjha-elastic/elasticsearch into enhancement/sentinel_one-add_ilm_delete_index
kcreddy
added
>non-issue
:Security/Authorization
|
Pinging @elastic/es-security (Team:Security) |
elasticsearchmachine
removed
the
needs:triage
kcreddy
added
needs:triage
elasticsearchmachine
removed
the
needs:triage
|
@elasticsearchmachine test this please |
|
@elasticsearchmachine test this please |
|
Heya @mohitjha-elastic The PR description mentions the need to delete, but the changes include additional permissions being granted, is this intentional? Could you provide some additional context? New New |
Thanks @kc13greiner! I have updated the PR description. The SentinelOne Sorry for any confusion but the access for the |
@kc13greiner, the access for This PR only adds |
|
++ thank you for the additional context! We can allow these new permissions on the sentinel one indicies, LGTM! |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…33793) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
…33793) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
…33793) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
…134114) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
…134113) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
…134112) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
…134111) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
mohitjha-elastic
deleted the
enhancement/sentinel_one-add_ilm_delete_index
branch
…33793) (elastic#134113) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
…33793) (elastic#134113) This PR focuses on the short term solution which add the logs-sentinel_one.application-* and logs-sentinel_one.application_risk-* indices under the kibana_system role with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required. Current behavior: It shows permission issue while deleting the index. (cherry picked from commit bfde47a)
4 participants
PR Description:
This PR focuses on the short term solution which add the
logs-sentinel_one.application-*andlogs-sentinel_one.application_risk-*indices under thekibana_systemrole with deletion privileges to prevent a failed deletion error when the index enters the deletion phase for the ILM lifecycle, in upcoming PR. As it ships transform pipeline too hence read, write permissions are also required.Current behavior:
It shows permission issue while deleting the index.
Closes - elastic/kibana#235996
Similar Issues : elastic/kibana#197390, #131825