santerikainulainen/ansible-role-elasticsearch
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update readme to include versioned install command

Browse source 
In #538 it was discovered that recent versions of the ansible galaxy
command will fail if there aren't semver compatible releases in the
history.

The error says:

> Please contact the role author to resolve versioning conflicts, or
> specify an explicit role version to install.

Removing the old releases is not such a great idea so instead updating
the install command is the best option.

Fixes: #538
This commit is contained in:
Michael Russell 2019-03-11 23:07:01 +10:00
parent 509a91878f
commit 81f30e7972
No known key found for this signature in database
GPG key ID: A90C1696496085FE
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -21,7 +21,7 @@ This role uses the json_query filter which [requires jmespath](https://github.co
Create your Ansible playbook with your own tasks, and include the role elasticsearch. You will have to have this repository accessible within the context of playbook. Create your Ansible playbook with your own tasks, and include the role elasticsearch. You will have to have this repository accessible within the context of playbook.
```sh ```sh
ansible-galaxy install elastic.elasticsearch ansible-galaxy install elastic.elasticsearch,6.6.0
``` ```
Then create your playbook yaml adding the role elasticsearch. By default, the user is only required to specify a unique es_instance_name per role application. This should be unique per node. Then create your playbook yaml adding the role elasticsearch. By default, the user is only required to specify a unique es_instance_name per role application. This should be unique per node.