Skip to content

Conversation

tbauriedel
Copy link
Member

@tbauriedel tbauriedel commented Sep 23, 2025

PR to add some refactoring development. Will grow over time.
Part of #396

A list of changes can be found below.


fixes #316

@tbauriedel tbauriedel self-assigned this Sep 23, 2025
@tbauriedel tbauriedel added the breaking-change PR / Issue / Fix that will implement a breaking change! label Sep 23, 2025
@tbauriedel tbauriedel added this to the 0.1.0 milestone Sep 23, 2025
@tbauriedel tbauriedel changed the title Rename elasticstack_full_stack to elasticstack_collection_managed Review and refactoring of the collection Sep 23, 2025
@tbauriedel tbauriedel added the quality Changes that will not affect the technical details, but add some more quality to the code, docs, ... label Sep 23, 2025
There were an known issue with EL 9 that has been solved by elastic
itself. We dont need it anymore.

elastic/elasticsearch#85876
This variable is only part of the `repos` role. There is no need to
define it inside the `elasticstack` role.
`repos_deb_remove_legacy_key` can be used to remove an existing key from
the trusted.gpg keyring
Keep an straight line for comments in templates, newlines in yaml files
and yaml syntxa in general
afeefghannam89
afeefghannam89 previously approved these changes Sep 25, 2025
Copy link
Member

@afeefghannam89 afeefghannam89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the idea, thanks. I think will document the following variable in the documentation PR, will you?
elasticstack_hosts_elasticsearch
elasticstack_hosts_logstash
elasticstack_hosts_kibana

@tbauriedel
Copy link
Member Author

I like the idea, thanks. I think will document the following variable in the documentation PR, will you? elasticstack_hosts_elasticsearch elasticstack_hosts_logstash elasticstack_hosts_kibana

Sure. This will be documented. For now I just wanted to see if everything works and let the pipelines run :D

There are tasks that are doing things with other tools of the
collection (e.g: after changing certificates in elasticsearch, we need
to restart kibana).
This tasks will be moved to the global role "elasticstack" and can be
called by via 'notify'.
Also, global handlers will only do something when
`elasticstack_collection_managed` is true (means the whole stack is
managed by the collecion)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change PR / Issue / Fix that will implement a breaking change! quality Changes that will not affect the technical details, but add some more quality to the code, docs, ...
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Question]: Rename full_stack variable - Please let us know your ideas
2 participants