Comment 1 for bug 1528093

Adding ansible to global requirements would be required to fix this. If we add a project to requirements.txt that isn't in global requirements, the requirements bot removes it later.

I believe it is policy of the global requirements project not to permit GPLV3 licensed software in the global requirements. I'm not clear there is anything we can do here, as the foundation is crystal clear that GPLV3 code is not permitted as a dependency.

The way we use Ansible is not as a dependency but as a piped process executed in a separate process. Essentially using GPLv3 software this way is compatible with the ASL2.0. This type of usage of GPLv3 is safe from licensing concerns from what I can tell on the legal mailer. IANAL - consult your legal counsel on this point or the foundation legal list.