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
An ansible project, whether it be a playbook with an adjacent collection directory with a requirements file, or a collection, may reference and require other collections.
What do you think about a rule that checks for outdated dependencies that have a hard-coded version?
This might need to be an opt-in rule since it would need to hit the galaxy/AH server and not be fast.
also- parsing the version in the requirements file might be tricky....
but, for a CI pipeline, I could see this being very useful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
An ansible project, whether it be a playbook with an adjacent collection directory with a requirements file, or a collection, may reference and require other collections.
What do you think about a rule that checks for outdated dependencies that have a hard-coded version?
This might need to be an opt-in rule since it would need to hit the galaxy/AH server and not be fast.
also- parsing the version in the requirements file might be tricky....
but, for a CI pipeline, I could see this being very useful.
Beta Was this translation helpful? Give feedback.
All reactions