We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In my previous PR #724, I added support for the DS template lifecycle. However, this is insufficient to update the existing DS lifecycle.
https://www.elastic.co/guide/en/elasticsearch/reference/current/tutorial-manage-existing-data-stream.html
I can implement new resources for these APIs
https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-get-lifecycle.html https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-put-lifecycle.html https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-delete-lifecycle.html
usage would be:
resource "elasticstack_elasticsearch_data_stream_lifecycle" "ds_lifecycle" { name = "ds-name" data_retention = "5d" enabled = true downsampling=[...] }
Is it OK for you to do it this way?
The text was updated successfully, but these errors were encountered:
Sounds perfect @aizerin!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
In my previous PR #724, I added support for the DS template lifecycle. However, this is insufficient to update the existing DS lifecycle.
https://www.elastic.co/guide/en/elasticsearch/reference/current/tutorial-manage-existing-data-stream.html
I can implement new resources for these APIs
https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-get-lifecycle.html
https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-put-lifecycle.html
https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams-delete-lifecycle.html
usage would be:
Is it OK for you to do it this way?
The text was updated successfully, but these errors were encountered: