Skip to content

ansible-tower-0.9.1

Compare
Choose a tag to compare
@john-westcott-iv john-westcott-iv released this 05 Nov 00:01
· 66 commits to master since this release

My apologies for the delay in getting this fix out. One of the things which took a while to setup was a more robust testing environment. Hopefully issues like the login issues with the last release will be able to be caught before they are released. Thanks the community for all of the help with the following fixes as well as to the Ansible Tower Engineering team for working with me on a better way to achieve the task at hand.

  • Fixing authentication issues. We initially were trying to determine the version number of Tower/AWX and then make a decision on authentication method. We now do it like tower-cli does by checking for /api/v2/o to determine if we need to authenticate with an oAuth token or a legacy token type. Thanks to @tisluk for the Pull Request starting this fix.
  • In addition, we added more logging message when a Tower instance is set to debug as to what is happening with authentication.
  • Fixed some typos in log messages.
  • Fixed issue if you have Force Trust cert enabled but you are connecting to an AWX instance on http.
  • The plugin now attempts to give you more details if it receives a 403 (Unauthorized) from the instance.
  • Fixed an issue where newer versions of Tower failed if credentials were not in integer format. Thanks to @jmcshane for the Pull Request. JENKINS-54503
  • The plugin now returns JOB_ID, JOB_URL and JOB_RESULT back to Jenkins. Thanks to @tisluk for the Pull Request.
  • The plugin can now be configured to not fail a job if a Tower execution fails. Thanks to @tisluk for the Pull Request.