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

RHACS: default domain for email recipients for dynamic notifications

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • RHACS
    • False
    • None
    • False
    • Not Selected

      Business Problem:

      Customer uses a namespace annotation to provide contact information, in the form of a userid without "@" symbol or domain.

      example:

      annotations:

          email:first.last

       Because this value does not constitute a valid email address, ACS cannot send notifications to recipients dynamically.

      Customer would like to be able to supply a configurable default domain per integration that would allow @example.com to be appended to the user id found in the annotation value. We have customers who have multiple domains; we should design for that as well.
       

      Use Cases:

      Each namespace in all clusters expresses ownership through user id, and needs transformation of user id -> email address by appending a domain.
       

      Key Functionality:

      Email integration configuration should support a "default domain" and the ability to specify a different domain per namespace or namespace pattern if the annotation value does not already have a fully qualified email address.

      Notifications should be sent to recipient address constructed from "value in specified annotation key" + "@" + "domain specified" for that namespace

       

      Benefits:

      Customer can re-use existing ownership information

      ACS could potentially use labels for userid instead of annotations, although that is not being requested here. labels do not support "@" symbol required for a fully qualified email address, but could store a userid.

      Acceptance criteria:

      • Emails specified in a namespace annotation are updated with the desired domain name so that emails can be sent
      • If a default domain name is specified, it will be applied to all namespace annotations
      • If multiple domain names are specified, they will be applied to the specified namespace
      • Notifications sent by email from different namespaces are successfully sent to the recipient specified in the namespace annotation

      [Describe the key features that need to be covered by the feature to be able to satisfy the customer]

      Implementation Suggestions (optional):

      • Integration: [Specify any existing systems or tools that the new feature should integrate with]

       

      • Dependencies: [Describe any dependencies on other 3rd party integrations or OCP components]

       

      • User Experience: [Provide suggestions for designing the UI to optimize usability. Highlight other relevant aspects of the user experience ]

       

      Timeline:

      [Specify the preferred implementation date or any specific deadlines for the feature implementation]

       

      Please use the following Jira fields to complete this Feature Request

      1. [Jira Field] Summary Required: [Provide a clear and concise name/description for the feature]
      2. [Jira Field] Description:
      3. [Jira Field] Component:
      4. [Jira Field] Priority: [Indicate the importance or urgency of the feature on a scale of High, Medium, or Low]
      1. [Jira Field] Supporting Documentation:
         
      1. [Attach any relevant documents, research, or supporting materials that provide additional context or information]

       

       

              dcaspin@redhat.com Doron Caspin
              cporter@redhat.com Christopher Porter (Inactive)
              Anjali Telang, Boaz Michaely, Doron Caspin, JP Jung, Maria Simon Marcos, Shubha Badve
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: