Closed AMeng closed 8 years ago
+1
As work around, you should be fine to fix it with commits.
$ cat requirements.yml
- src: https://github.com/FloeDesignTechnologies/ansible-haproxy
version: c35fd3358728a220f7c981cb798158adefa8015c
name: haproxy
$ ansible-galaxy install -r requirements.yml
- executing: git clone https://github.com/FloeDesignTechnologies/ansible-haproxy haproxy
- executing: git archive --prefix=haproxy/ --output=/var/folders/rd/9qyzysds1lbfvvnc8pwrwhw00000gn/T/tmp3JYFiV.tar c35fd3358728a220f7c981cb798158adefa8015c
- extracting haproxy to roles.galaxy/haproxy
- haproxy was installed successfully
$ ansible-galaxy list
- haproxy, c35fd3358728a220f7c981cb798158adefa8015c
Compare to install role directly.
$ ansible-galaxy install info.haproxy
- downloading role 'haproxy', owned by info
- downloading role from https://github.com/Pheromone/ansible-haproxy/archive/master.tar.gz
- extracting info.haproxy to roles.galaxy/info.haproxy
- info.haproxy was installed successfully
$ ansible-galaxy list
- info.haproxy, master
I tagged this release 1.0 : https://galaxy.ansible.com/FloeDesignTechnologies/haproxy/ Thanks everyone, sorry for the wait.
Would it be possible to get a versioned release of this role? Its important for many users to be able to lock down the role to a specific version, instead of always pulling the master branch.
According to the Galaxy Docs, this should be as easy as just adding tags in GitHub.
This allows users to lock in a specific release in their
requirements.yml
like so: