With this issue we define the global retention for data stream lifecycle and we track the progress.
We would like to introduce a global retention configuration that would enable the project owners to introduce default and max retention for all data streams managed by data stream lifecycle.
The work will be completed in the following steps:
[x] Introduce the cluster state metadata that will store the global retention, this is effectively not adding any functionality since there is no way to add global retention. (https://github.com/elastic/elasticsearch/pull/106170).
[x] Introduce PUT, GET, DELETE REST APIs to enable the user with the correct privileges to manage the global retention. With this PR the feature becomes available and it will include docs and tests (https://github.com/elastic/elasticsearch/pull/105682).
[ ] Add telemetry about the global retention
We propose the above sequence of steps to ensure that the functionality will not be exposed to the users until its complete.
Description
With this issue we define the global retention for data stream lifecycle and we track the progress.
We would like to introduce a global retention configuration that would enable the project owners to introduce default and max retention for all data streams managed by data stream lifecycle.
The work will be completed in the following steps:
PUT
,GET
,DELETE
REST APIs to enable the user with the correct privileges to manage the global retention. With this PR the feature becomes available and it will include docs and tests (https://github.com/elastic/elasticsearch/pull/105682).We propose the above sequence of steps to ensure that the functionality will not be exposed to the users until its complete.