Uploaded image for project: 'Ansible Automation Platform RFEs'
  1. Ansible Automation Platform RFEs
  2. AAPRFE-1554

Allow installation of older AAP version via the operator

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 2.4
    • platform-operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      1. What is the nature and description of the request?
        The AAP operator provides the ability to select the version upon deployment, however, no matter the version selected it always installs the latest available version.
      1. Why does the customer need this? (List the business requirements here)
        Customers who pin to select versions of AAP after testing/QA are unable to deploy the tested version of AAP before a production rollout if a new release was cut before upgrading all of their production environments. 

      This could also be useful for support in being able to replicate bugs that happen inside of customer environments by deploying the same version the customer is running. 

      1. How would you like to achieve this? (List the functional requirements here)
        Other operators such as ACS/ACM offer this capability, but I am unsure why the AAP operator defaults to the latest instead of the selected version upon deployment. 
      1. List any affected known dependencies: Doc, UI etc..
        AAP Operator
      1. Github Link if any
        N/A

      Alternatively, if this is how we want things it might be worth removing the dropdown menu all together. I have attached a screenshot of the dropdown in reference for clarity. This was originally raised as a bug in AAP-25550.

            rhn-sa-pgriffiths Phil Griffiths
            rh-ee-mtipton Michael Tipton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: