Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7464

Ability to optionally define project scope while integrating with Google Registries

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Goal Summary:

      Customers have requirement to have more than one project associated with Google registry integration. Today, ACS enforces project scope (see pic attached). This makes the integration cumbersome for customer to configure.

       

      Goals and expected user outcomes:

      Provide project scope as optional for customers while integrating with Google Artifact Registry

      Acceptance Criteria:

      Image integration with Google Artifact Registry available without the need to add per project scope. 

      Success Criteria or KPIs measured:

      Registry integration can be setup with Google Artifact Registry for multiple projects

      Errors handled gracefully 

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

      <your text here>

      Out of Scope (Optional):

      High-level list of items that are out of scope. Initial completion during Refinement status.

      <your text here>

              atelang@redhat.com Anjali Telang
              rhn-support-bsmitley Brandon Smitley
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None