-
Notifications
You must be signed in to change notification settings - Fork 331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible-galaxy install --force no longer replaces roles #74
Comments
Fixed in by Ansible PR #23391 |
I believe, we still have a problem with "updating" using the We have a situation in a cluster auto-update strategy that makes a playbook fail, because an
This is due to the fact that Rather than Has something like that been discussed before? Is that maybe planned already? |
Related issues:
|
I believe OP's issue been fixed at some point. Would still be nice to have the
Starting galaxy collection install process
Process install dependency map
Starting collection install process
'kewlfft.aur:0.10.0' is already installed, skipping.
Starting galaxy role install process
- changing role gantsign.visual-studio-code-extensions from 2.4.0 to unspecified
- downloading role 'visual-studio-code-extensions', owned by gantsign
- downloading role from https://github.com/gantsign/ansible-role-visual-studio-code-extensions/archive/2.4.0.tar.gz
- extracting gantsign.visual-studio-code-extensions to /root/.ansible/roles/gantsign.visual-studio-code-extensions
- gantsign.visual-studio-code-extensions (2.4.0) was installed successfully
- changing role geerlingguy.certbot from 4.1.0 to unspecified
- downloading role 'certbot', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-certbot/archive/5.0.0.tar.gz
- extracting geerlingguy.certbot to /root/.ansible/roles/geerlingguy.certbot
- geerlingguy.certbot (5.0.0) was installed successfully
- changing role geerlingguy.postgresql from 3.1.1 to unspecified
- downloading role 'postgresql', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-postgresql/archive/3.2.1.tar.gz
- extracting geerlingguy.postgresql to /root/.ansible/roles/geerlingguy.postgresql
- geerlingguy.postgresql (3.2.1) was installed successfully
|
From @jxn on April 13, 2017 18:10
After the version bump to 2.3.0, it seems install --force no longer forces an overwrite. We have been using this to "upgrade" roles stored in git, but they are no longer pulled in.
Here's the command used:
ansible-galaxy install --force -r ansible/requirements.yml -p ansible/roles/
Here's an example requirements.yml
Previously, when we pushed new role updates to master, these would be overwritten in the 'ansible/roles' directory with the above command. Now, these are not updated until we manually delete the roles in that folder. We get the following output:
As far as I can tell, force no longer does anything as of 2.3.0
Copied from original issue: ansible/galaxy-issues#249
The text was updated successfully, but these errors were encountered: