Supporting Tower 3.2.x

[jameswnl]

Credentials

Major Changes

• Tower 3.2.x upgrade will split up a machine credential which has vault_password value and both will remain associated to job_templates (if any)
  ** For us, we'll create/update accordingly (have to test and confirm if the new machine credential will keep the original ID.
• Tower 3.2.x upgrade will drop azure_classic and rackspace credentials (and previously associated job_templates will just lose them
  ** Dropping azure classic and rackspace credential types manageiq#16936 and Dropping azure classic and rackspace credential types #58
  ** After upgrade, refresh will destroy them
• Other newly added:
  ** Vault
  ** Ansible Tower
  ** Insights
  ** rhev
  ** custom credential type (Custom credentials will not be managed by the V1 API)

Todo

• UI changes for embedded Ansible items will need a new credential drop-down for Vault. (
  • Services Template: Add Vault credentials to the UI for Embedded Ansible  manageiq-ui-classic#3468
  • Automate Method Type: (Same as above)
• Add Vault credential in Service summary screen
  • Add vault credential to factory and provision_job_options. manageiq#17207
  • Add vault credential to Ansible Tower Job. #70
• Back-end: Add vault credential support to Ansible playbook service template Add vault credential support to Ansible playbook service template. manageiq#17184
• Back-end: Add vault credential support to Ansible Automate Method Type Add vault credential support to automat playbook method. manageiq#17192
• Clarify if upgrade and split machine credential will keep the original ID
  • Test the upgrade scenario
• Provider code changes
  • vault credential type
    • PR Tower 3.2.2 vault credential types manageiq#16825
    • PR Tower 3.2.2 vault credential type #54
  • rhev credential type
    • this can be only partially supported through the Tower API V1
    • The support for the optional field ca file location can only be done when move to consume from API V2
    • PR Tower Rhv credential type #62
    • PR Tower Rhv credential type manageiq#17044
    • PR Add host field to rhv_credential #69
  • drop Rackspace/Azure Classic credential types
    • PR Dropping azure classic and rackspace credential types manageiq#16936
    • PR Dropping azure classic and rackspace credential types #58

Others

• Investigate usage of custom credential (e.g. supporting Azure classic?)

[jameswnl]

@gmcculloug @bdunne @syncrou

[gmcculloug]

@jameswnl Thanks for capturing these notes.

I would suggest adding an item in the Todo section for "will machine credential will keep the original ID". Also, I assume there is work to enable the UI to CRUD the new Vault credentials. From what I understand this is backend work, but you would know better.

Another item, but maybe not a Todo here is to investigate custom credentials more so we can support types like Azure through this new feature.

[gmcculloug]

[gmcculloug]

@jameswnl I think we have addressed all the areas here, if you agree I think we can close this issue.

[jameswnl]

@gmcculloug I've added a todo to test the upgrade scenario and its impact on the converted/dropped credentials.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!