You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2024. It is now read-only.
The elasticsearch module provides this esentially as follows:
A selection of Puppet variables is written to a YAML file on the agent host (namely to /etc/elasticsearch/elasticsearch.yml
Custom Facts are created, which read this YAML file.
For Kallithea, we will only have to remember the path $venv to its virtualenv (but be prepared that there are multiple instances and thus multiple virtualenvs), then the Kallithea version can be computed by running ${venv}/bin/pip show kallithea | grep '^Version:' | cut -d' ' -f2 or something like that
The implementation of the `kallithea_version` fact has been heavily
inspired by the elasticsearch/elasticsearch module.
The idea is to get the Kallithea version from the output of `pip version
kallithea`. However, the problem is that the path to the pip binary of
Kallitheas virtualenv depends on `$kallithea::install::venv`, which is
unknown on the puppet client. Therefore, we first store this information
on the Puppet client in `/etc/kallithea.yml` which enables us to read
them later, when the `kallithea_version` fact needs to be evaluated.
The concept of persisting interesting information on the client side
seems to be so useful, that I have generalized this by means of the
`settings_store` class and the `stored_setting` defined type. They are
based on the richardc/datacat module, which allows us to merge the data
given by multiple `stored_setting` declarations before they get written
to `/etc/kallithea.yml`.
refs #10
No description provided.
The text was updated successfully, but these errors were encountered: