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
When using tar files to download dependencies the url for the dependency can change, but if the role name used in the dependency file is not changed, it is considered the same dependency and not re-downloaded.
This means to ensure the correct dependency is downloaded either --force-with-deps has to be used everywhere (since sub dependencies won't be updated if you just use --force) or you have to change the role name, forcing you to update the tasks using it.
If you do update the role name you'll slowly fill your ~/.ansible/roles with every version of the role you've ever used.
I purpose that either:
meta/main.yml should be able to hold a version number which is checked against.
the url used to download the role is stored beside the role in ~/.ansible/roles and checked against when a new role is installed with the same name.
The text was updated successfully, but these errors were encountered:
When using tar files to download dependencies the url for the dependency can change, but if the role name used in the dependency file is not changed, it is considered the same dependency and not re-downloaded.
This means to ensure the correct dependency is downloaded either
--force-with-deps
has to be used everywhere (since sub dependencies won't be updated if you just use--force
) or you have to change the role name, forcing you to update the tasks using it.If you do update the role name you'll slowly fill your
~/.ansible/roles
with every version of the role you've ever used.I purpose that either:
meta/main.yml
should be able to hold a version number which is checked against.~/.ansible/roles
and checked against when a new role is installed with the same name.The text was updated successfully, but these errors were encountered: