9185056efe
In this PR we remove unused code including relating to the global data retention with APIs implementation: - The transport action for updating, deleting and retrieving the global retention. - The `DataStreamGlobalRetention` from the cluster state (this should be bwc safe because we never exposed the APIs to add a data stream lifecycle to the cluster state). - Make unused privileges monitor and managing global retention a noop. - Remove cluster state update tasks. The kept `DataStreamGlobalRetentionResolver` considering it could hold and provide the global retention from the settings when we implement it. We just renamed it to DataStreamGlobalRetentionProvider for now to better match what it does. The factory retention settings should still work after this change. |
||
|---|---|---|
| .. | ||
| auditing | ||
| authentication | ||
| authorization | ||
| ccs-clients-integrations | ||
| images | ||
| operator-privileges | ||
| reference | ||
| securing-communications | ||
| configuring-stack-security.asciidoc | ||
| enroll-nodes.asciidoc | ||
| es-security-principles.asciidoc | ||
| fips-140-compliance.asciidoc | ||
| fips-java17.asciidoc | ||
| index.asciidoc | ||
| limitations.asciidoc | ||
| security-manual-configuration.asciidoc | ||
| troubleshooting.asciidoc | ||
| using-ip-filtering.asciidoc | ||