Logstash version number structure

[psteinmetzcid]

We added elasticstack_version to inventory as variable to all Hosts in the Cluster.
We have found that the Version number for Logstash in ubuntu is not the same as for all other products.

The Structure is e.g. '1:8.8.1-1' for Version 8.8.1.

I think it would be good to rebuild the task that compiles the version number for Logstash. This way, elasticstack_version does not have to be maintained multiple times in the playbook.

[martialblog]

Hi, thanks for the hint. We will look into this.

Like you said, a workaround would be specify different scoped variables for the version:

roles:
   - role: netways.elasticstack.kibana
     vars:
        elasticstack_version: 1.2.3
   - role: netways.elasticstack.logstash
     vars:
        elasticstack_version: 2.3.4

[martialblog]

@danopt @afeefghannam89 FYI

[widhalmt]

Mixing different versions of tools in the Elastic Stack doesn't work well. Not from an Ansible point of view, but from Elastic Stack.

Honestly, I'm a bit tired of different versioning schemes. If I were better in writing modules I really considered building a module that just spills out the correct versioning string for the current OS. Having to maintain a gazillion of different tasks to rename the files is cumbersome but for now I don't have a better idea.

Thanks none the less for showing us that Ubuntu needs some extra work, though. We'll discuss how we want to proceed. If we will just add Ubuntu or if we take a step back and make a solution that will work more globally.