Automate Ansible Tower license about tower-operator HOT 4 CLOSED

@tylerauerbeck - That would be nice to be able to do; I just don't know the best mechanism for doing so. Maybe a secret mounted into a directory that could be referenced and loaded in once Tower is running?

I don't know if there's actually any way to specify a license outside of the admin UI workflow—that's all I can find documented in the docs :/

from tower-operator.

This can actually be done via the API and we've got a role that does that here: https://github.com/redhat-cop/infra-ansible/tree/master/roles/ansible/tower/config-ansible-tower-license

Happy to help roll this into the operator. Just wasn't sure where this operator was looking to draw the line. My thought would be to use a secret like you mention though. I think the thing to think about though may be what happens when you want to update your license. Happy to get the initial functionality added though if you'd be willing to have it.

from tower-operator.

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

from tower-operator.

(Note that this issue might not be a fit for the awx operator either, as it's focus seems to be shifting to AWX-first and will only 'experimentally' support Tower until there's an officially supported Tower operator.

Now that the operator is being maintained in the Ansible namespace, I am not going to maintain this project anymore (as I consider it a historic artifact which was used to as a base for the ansible-namespace version, and I'm redirecting all issues and PRs to the Ansible-maintained version: https://github.com/ansible/awx-operator

from tower-operator.