Enable the Send Email node for Orchestration Pipelines

You can enable the Send Email node functionality in Orchestration Pipelines.

Who needs to complete this task?
Instance administrator: An Instance administrator must complete this task.
Before you begin

You can run the commands in this task exactly as written if you set up the environment variables for IBM® Software Hub Control Center. For instructions, see Setting up environment variables for IBM Software Hub Control Center.

In addition, ensure that you source the environment variables before you run the commands in this task.

About this task
Edit the watson-pipelines-config configmap Kubernetes resource in order to enable functionality of the Send Email node in the pipeline.

Procedure

Follow the steps to enable the Send Email node:
  1. Log in to Red Hat® OpenShift® Container Platform as a user with sufficient permissions to complete the task:
    ${OC_LOGIN}
  2. Patch the watson-pipelines-config configmap Kubernetes resource on the cluster with the hidden_components environment variable set to the empty list value: 
    oc patch configmap watson-pipelines-config -n ${PROJECT_CPD_INST_OPERANDS} --type=merge -p '{"data": {"hidden_components":"[]"}}'
    The output of the following command:
    configmap/watson-pipelines-config patched
  3. Confirm if the hidden_components value was applied to the watson-pipelines-config config map by running:
    oc get cm -n ${PROJECT_CPD_INST_OPERANDS} watson-pipelines-config -o yaml | yq -r .data | grep hidden_components
    If everything is correct, the output of the command is:
    hidden_components: '[]'
  4. Check the Orchestration Pipelines pipelines asset UI that the Send palette node is visible.

Revert procedure

If you want to revert the changes of enabling the Send Email node, run the following steps:
  1. Log in to Red Hat OpenShift Container Platform as a user with sufficient permissions to complete the task:
    ${OC_LOGIN}
  2. Patch the watson-pipelines-config configmap Kubernetes resource on the cluster with the hidden_components environment variable set to the null value: 
    oc patch configmap watson-pipelines-config -n ${PROJECT_CPD_INST_OPERANDS} --type=merge -p '{"data": {"hidden_components":null}}'
  3. Confirm if the hidden_components value is not visible in the watson-pipelines-config config map by running:
    oc get cm -n ${PROJECT_CPD_INST_OPERANDS} watson-pipelines-config -o yaml | yq -r .data | grep hidden_components
    There should be no output from the terminal.
  4. Check the Orchestration Pipelines pipelines asset UI that the Send palette node is not visible.