In Ansible Tower 3.2, while using the AWS credential stored in Tower as
AWS_SECRET_KEY we are now getting empty values when running a job that utilizes these values passed to the environment. This was working fine in Ansible Tower 3.1.x.
- Ansible Tower >=3.2.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.