Uploaded image for project: 'Insights Experiences'
  1. Insights Experiences
  2. HMS-1690

Address Azure Launch technical debt

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • hms-1.4, hms-1.3
    • None
    • Provisioning
    • None
    • Azure tech improvements
    • 0% To Do, 0% In Progress, 100% Done
    • True

      Goal:

      • Split Azure launching to steps that make sense to a User
      • Make it clear for user what Resource group is going to be used
      • Implement support for naming the instances in API (not UI)
      • Implement Source availability check

      Acceptance Criteria:

      • UX for Azure doesn't raise an eyebrow

      Open questions:

      • How should we deal with the resource groups in IB and Prov?
      • Should we first migrate image builder to use the same tenant (redhat.com)?

            oezr@redhat.com Ondrej Ezr
            oezr@redhat.com Ondrej Ezr
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: