Hi Team,
How do we build custom execution environments with ansible-builder v3 when Galaxy collections include loose dependencies like ansible-pylibssh>=0.2.0
? Pip is always invoked with --require-hashes
, which rejects any non-==
specifiers. Should users be pinning these themselves, or is ansible-builder expected to handle this case?
Any help on how to create a custom AWX EE image would really help as I have been stuck in this for over a week.
Thanks in advance!