Allow $version to set an specific release about puppet-elastic_stack HOT 5 CLOSED

This would need to be implemented in the Elasticsearch module, if it isn't already.

This module only deals with package repositories, which don't even have minor versions. They just have "5.x", "6.x" etc. Really, the line:

elasticsearch::repo_version: '1.7.6'

is quite strange. That should never have been called the "repo version", it is the "package version".

@tylerjl, @fatmcgav: do you have any suggestions for how this should be handled now?

from puppet-elastic_stack.

So pulling this apart, I'm seeing a few questions:

• First, version 1 just isn't well-supported any more (it's very, truly dead from an end-of-life perspective), so I don't think you'll have much luck using elastic_stack::repo with v1 repositories - the module constructs repositories of the "${major_version}.x" form, and the 1.x series repositories looked like 1.7 instead.
• If you need to keep pinning elasticsearch versions, the elasticsearch::version parameter is still there for you - the Elasticsearch module delegates repo-level things to this module now, so there's no repo_*-level parameters to tinker with in that module.

Do let me know if I'm misunderstanding the intent here.

from puppet-elastic_stack.

@tylerjl yes, we can still pin the version with the elasticsearch module, however, there is no way to set a custom repository at the moment (we have to declare an Apt resource in the role for voiding this issue).

I know, super old release..

from puppet-elastic_stack.

Hmm, can you not set elasticsearch::manage_repo: false and just manage an elastic repository yourself? If the Elasticsearch module is causing you to work around broken dependencies when you ask it to not manage any repositories, that should be something we fix.

from puppet-elastic_stack.

We are managing the repository by ourselves now, that worked around the issue for this ancient stack.

from puppet-elastic_stack.