Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-2522

Provide usable way of setting extensions image name and namespace for external DB driver in Operator UI

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 7.7.0.GA
    • None
    • Cloud
    • None
    • 2020 Week 04-06 (from Jan 20)

      dward-se-jboss rhn-support-fspolti rhn-support-rromerom tohughes vidya_iyengar rhn-support-hjoy FYI. I would also very much appreciate David's and Filippe's and Tommy's (and Ruben's if he is interested in this area) input about what approach is best.

      Currently, When you select external DB, the yaml will have a fixed extension image name and namespace as environment vars:

      env:
      name: EXTENSIONS_IMAGE
      value: 'jboss-kie-oracle-extension-openshift-image:12cR1'
      name: EXTENSIONS_IMAGE_NAMESPACE
      value: rhpam-externaldb

      This is not usable for the following reasons:

      (1) The image name is always set to jboss-kie-oracle-extension-openshift-image, even if the selected driver is not oracle (for example, db2), making other drivers unusable as the build script appears to fix the name

      (2) The extension image settings are not needed when the mysql or postgresql driver is used

      (3) I am not sure if the user always has the option, security-wise, to create or modify a namespace with the specific name "rhpam-externaldb"

      So this approach does not work, and a version that is workable must be implemented. My suggestions would be:

      (a) Back out the current change and offer new UI fields for extensions image and extensions image namespace, visible only if the DB is set to external. If the fields are left empty just do not set the variables. In this way, the user will be reminded that they need to set the fields; but if they are really using the postgresql or mysql driver they will skip the action.

      (b) Back out the current change and expect the user to set the environment variables like they set any other environment variables. However, if the DB is set to external and the driver is not set to either mysql or postgresql, verify that these two environment variables are set, and if not, display an error message.

      (c) Keep the current change but modify it so that instead of "jboss-kie-oracle-extension-openshift-image" the image name is set to "jboss-kie-$DRIVER$-extension-openshift-image". The disadvantage is that the issue in (3) remains: is there a guarantee that the user can use the specific namespace called "rhpam-externaldb"?

      (d) A combination of (a) and (c). Create the two new UI fields if the database is set to external, but prepopulate them with "jboss-kie-$DRIVER$-extension-openshift-image" and "rhpam-externaldb". Clear them if the driver is set to postgresql or mysql. Let the user edit in all cases.

      While I would prefer option (d), I understand it might be too much work to implement and maintain this option, so I would really appreciate Dev input here.

              swkale Swati Kale
              mramendi Mikhail Ramendik
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: