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
AWX and ansible tower are moving to using execution environments (containers, basically) versus virtualenvs, as such ansible-builder has been put together to build execution environments. ansible-builder collection documentation shows what happens, but basically if a collection has a requirements.txt said python requirements are installed into the execution environment thus easing maintenance of the execution environment.
I'd like to propose that the community.general collection begin a requirements.txt fie to gather python module requirements, thus allowing easier installation into an EE.
Issue Type
Feature Idea
Component Name
all
Additional Information
No response
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
This is quite a huge task, since community.general has a huge amount of plugins and modules. Keeping a requirements file up-to-date for such a collection is quite a task.
Summary
AWX and ansible tower are moving to using execution environments (containers, basically) versus virtualenvs, as such ansible-builder has been put together to build execution environments. ansible-builder collection documentation shows what happens, but basically if a collection has a requirements.txt said python requirements are installed into the execution environment thus easing maintenance of the execution environment.
I'd like to propose that the community.general collection begin a requirements.txt fie to gather python module requirements, thus allowing easier installation into an EE.
Issue Type
Feature Idea
Component Name
all
Additional Information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: