Problem Description:

      We have deprecated synclists in favor or client-side requirements.yml (it is still supported but will be removed in a future release). We need to reflect this in the UI / UX.

      Pre-AAP2.4, The section Connect to Hub > Server URL showed the synclist url, now it shows the default url to get certified content.

      Proposed Solution:

      Connect to Hub > Server URL use new text: "Use this URL to configure the API endpoints that clients need to download certified content from Automation Hub. Synclists are deprecated in AAP 2.4 and will be removed in a future release, instead use client-side requirements.yml [more info]". And link to AAP synclist documentation in AAP-9650

      Change the displayed URL from "https://console.stage.redhat.com/api/automation-hub/" to "https://console.stage.redhat.com/api/automation-hub/content/published/" so it is clear they are getting content under "published" repo since now there are 2 repos to choose from.

      Remove this message at the top of every page: “The Automation Hub sync toggle is now only supported in AAP 2.0. Previous versions of AAP will continue automatically syncing all collections.”describe the problem this is solving

      Reword this text: "Use the Repositories page to sync collections curated by your organization to the Red Hat Certified repository in your private Automation Hub. Users with the correct permissions can use the sync toggles on the Collections page to control which collections are added to their organization's sync repository."

            [AAH-2335] UI to reflect synclist deprecation

            anastasiaratti there is at least slight benefit of having the "Server URL" section close to the "SSO URL" section since both of those urls need to be copy and pasted into the client config. See current page for full text https://console.redhat.com/ansible/automation-hub/token

            Not sure if the "Connect Private Automation Hub" section is meant as more of a summary or not. I'm ok with either way, just wanted to mention that.

            Andrew Crosby (Inactive) added a comment - anastasiaratti there is at least slight benefit of having the "Server URL" section close to the "SSO URL" section since both of those urls need to be copy and pasted into the client config. See current page for full text https://console.redhat.com/ansible/automation-hub/token Not sure if the "Connect Private Automation Hub" section is meant as more of a summary or not. I'm ok with either way, just wanted to mention that.

            awcrosby5 The text looks good to me. My one piece of feedback would be moving the "Server URl" section under "Connect Private Automation Hub" section, since "Connect Private Automation Hub" directly references "Server URl."

            Anastasia Ratti added a comment - awcrosby5 The text looks good to me. My one piece of feedback would be moving the "Server URl" section under "Connect Private Automation Hub" section, since "Connect Private Automation Hub" directly references "Server URl."

            semighdo@redhat.com I put the changes listed in the description, plus slight edits, into this Proposed_UX_Connect_to_Hub.png.

            anastasiaratti could you review the overall UX in that attachment, as far as what we want to communicate to the user viewing this page?

            Andrew Crosby (Inactive) added a comment - semighdo@redhat.com I put the changes listed in the description, plus slight edits, into this Proposed_UX_Connect_to_Hub.png . anastasiaratti could you review the overall UX in that attachment, as far as what we want to communicate to the user viewing this page?

              semighdo@redhat.com Shaiah Emigh-Doyle
              awcrosby5 Andrew Crosby (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: