Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-2345

Legacy galaxy redirect to mitigate url changes

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • Infrastructure

      Problem Description: Community users have linked to their collections and roles inside their blogs, documentation, etc.

      Links to collections and roles used in legacy galaxy will not resolve to the new beta galaxy which use different urls for the UI. While this is beyond "keep automation working" it would be good to mitigate broken links from the community.

      Proposed Solution:

      AAH-2342 has a proposed solution to beta-galaxy. In the event that does not get implemented, a change to legacy galaxy to allow community users to start using the longer paths would be a good thing:

            [AAH-2345] Legacy galaxy redirect to mitigate url changes

            John Mitchell added a comment -

            In lieu of this being fixed on beta, we are closing this for now.

            John Mitchell added a comment - In lieu of this being fixed on beta, we are closing this for now.

            Martin Hradil added a comment - - edited

            (AAH-2342 was implemented, URLs like https://beta-galaxy-dev.ansible.com/network/toolkit resolve to a list of matches now .. we may no longer need this?)

            Martin Hradil added a comment - - edited ( AAH-2342 was implemented, URLs like https://beta-galaxy-dev.ansible.com/network/toolkit resolve to a list of matches now .. we may no longer need this?)

              Unassigned Unassigned
              awcrosby5 Andrew Crosby (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: