Installing and Operating Fuse Online on OpenShift Container Platform

1. A user with cluster administration permissions:

   1. Downloads the installation script and related files.
   2. Registers a custom resource definition (CRD) at the cluster level, by using OpenShift oc client tool commands.
   3. Grants permission for one or more users to install Fuse Online in their projects, by using OpenShift oc client tool commands.

2. For each OpenShift project in which you want to install Fuse Online, a user who is granted permission to install Fuse Online:

   1. Decides whether to install a default Fuse Online environment or a customized Fuse Online environment. A customized Fuse Online environment enables one or more add-on features and/or implements one or more custom configuration settings.
   2. Downloads the installation script and related files.
   3. Optional. Edits the default-cr.yml file (provided in the Fuse Online download package) if a customized Fuse Online environment is wanted.
   4. Optional. Creates an OpenShift secret if an external database for persisting connection and integration definitions is wanted.
   5. Invokes the installation script.
   6. Confirms that Fuse Online is running.

Procedure

1. Download the package that contains the Fuse Online installation script from the following location:

   https://github.com/syndesisio/fuse-online-install/releases/tag/1.14

2. Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.14 directory contains the script and supporting files for installing Fuse Online.

3. Log in to OpenShift with an account that has cluster administration permissions. For example:

   oc login -u admin -p adminpwd

4. Confirm that you are properly connected by running the following command, which lists any custom resource definitions that are already registered in this cluster.

   oc get crd

   You are properly connected if there is no error message.

5. Register the custom resource definition at the cluster level by switching to the fuse-online-install-1.14 directory and invoking the following command:

   bash install_ocp.sh --setup

6. Confirm that registration was successful by running the following command again:

   oc get crd

   The output list of registered custom resource definitions should include syndesis.

7. In each project in which you want Fuse Online to be installed, grant installation permission to a user. For each project:

   1. Change to the project in which you want a user to be able to install Fuse Online. For example:

      oc project fuse-online-project

   2. Grant a user permission to install Fuse Online in that project. For example, the following command grants permission to install Fuse Online to developer user. After running this command, the developer user can install Fuse Online in the current project, which is fuse-online-project in this example:

      bash install_ocp.sh --grant developer

      Repeat these two commands for each OpenShift project in which you want to grant permission for Fuse Online installation. A single user can install Fuse Online in more than one project in the cluster. To enable this, change to another project and specify the same user, for example:

      oc project another-fuse-online-project
bash install_ocp.sh --grant developer

Procedure

1. If you did not already download the package that contains the Fuse Online installation scripts:

   1. Download it now from the following location:

      https://github.com/syndesisio/fuse-online-install/releases/tag/1.14

   2. Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.14 directory contains the scripts and supporting files for installing Fuse Online.

2. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

3. Open the fuse-online-install-1.14/default-cr.yml file in an editor.
4. Edit the default-cr.yml file so that it enables the features and sets the parameters that you want. To determine what you need to specify, see Descriptions of custom resource attributes that configure Fuse Online.
5. Save the default-cr.yml file.

Procedure

1. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

2. Create and save a resource file, for example, my-fuse-onling-secret-cr.yml) that contains the following:

   apiVersion: v1
   kind: Secret
   metadata:
     name: syndesis-global-config
     namespace: my-fuse-online-project
     type: Opaque
     data:
       POSTGRESQL_PASSWORD: base64-encoded-value

   Replace my-fuse-online-project with the name of the OpenShift project in which you plan to install the Fuse Online environment for which you are specifying an external database.

   Replace base64-encoded-value with a base64-encoded value that Fuse Online will use as the password for accessing the external database.

   For information about OpenShift secrets, see Secrets.

3. Add the secret to the cluster, for example:

   oc apply -f my-fuse-online-secret-cr.yml

Procedure

1. If you did not already download the package that contains the Fuse Online installation scripts:

   1. Download it from the following location:

      https://github.com/syndesisio/fuse-online-install/releases/tag/1.14

   2. Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.14 directory contains the scripts and supporting files for installing Fuse Online.

2. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

3. Switch to the OpenShift project into which you want to install Fuse Online, for example:

   oc project my-fuse-online-project

   Alternatively, when you run the installation script, you can specify, for example, --project my-fuse-online-project.

4. In the directory in which you downloaded the installation script, invoke the installation script:

   bash install_ocp.sh

   To learn about the installation script options, invoke the bash install_ocp.sh --help command.

5. Confirm that the syndesis custom resource that syndesis-operator used to install Fuse Online contains exactly the content that you want:

   1. Invoke the following command to display the syndesis custom resource content:

      oc describe syndesis/app

   2. Check the content of the custom resource.

      If it does not contain all of your updates, then there was probably a syntax error in the custom resource. You must uninstall Fuse Online and try again to define a valid custom resource. See Uninstalling Fuse Online from an OCP project.

6. Confirm that installation was successful:

   1. Display the OpenShift OAuth proxy log-in page at https://openshift-route.

      If you chose to let the installation script calculate the OpenShift route, then the script displays the calculated route near the end of its execution. Replace openshift-route with the value that the script provided.

      If you edited the default-cr.yml file to specify the routeHostname for Fuse Online, replace openshift-route with the route that you specified.

   2. If you are not already logged in to the OpenShift console, its log-in page appears. Enter your OpenShift user name and password to log in.

   The Fuse Online home page appears either immediately or after you log in to the OpenShift console.

Procedure

1. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

2. Switch to the OpenShift project that is running the Fuse Online environment whose configuration you want to change. For example:

   oc project my-fuse-online-project

3. Optional. Create a backup copy of the current settings in the syndesis custom resource, just in case you update and save incorrect content. For example, invoking the following command saves a backup in the syndesis_app_backup.yml file:

   oc get syndesis app -o yaml > syndesis_app_backup.yml

4. Invoke the following command to open the syndesis custom resource in an editor:

   oc edit syndesis

5. Edit the syndesis custom resource as needed.
6. Save the resource.

7. Wait two or three minutes, and then confirm that syndesis-operator was able to use your updates to the syndesis custom resource:

   1. Invoke the following command to display the content of the syndesis custom resource:

      oc describe syndesis/app

   2. Check the content.

      If the syndesis custom resource does not contain the settings that you need, edit it again to specify valid settings.

Procedure

1. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

2. Switch to an OpenShift project in which Fuse Online is running. You are enabling discovery for only this project. For example:

   oc project my-fuse-online-project

3. Edit the syndesis custom resource:

   1. Invoke the following command, which typically opens the resource in an editor:

      oc edit syndesis

   2. Edit the resource by setting managementUrlFor3scale to the URL for your 3scale user interface. The result looks like this:

      spec:
        components:
          server:
            features:
              managementUrlFor3scale: https://3scale-admin.apps.mycluster.com

   3. Save the resource.

4. Optional. To confirm that discovery is turned on for the project that you switched to, invoke the following command:

   oc describe dc/syndesis-server

   When discovery is turned on, the output from this command shows that the OPENSHIFT_MANAGEMENT_URL_FOR3SCALE environment variable is set to the URL that you specified in the custom resource.

Procedure

1. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

2. Switch to an OpenShift project in which 3scale discovery was enabled. For example:

   oc project my-fuse-online-project

3. Edit the syndesis custom resource:

   1. Invoke the following command, which typically opens the resource in an editor:

      oc edit syndesis

   2. Edit the resource by inserting a hash sign (#) at the beginning of the line that specifies the managementUrlFor3scale key and value. This makes the line a comment, which disables discovery. The result should look like this:

      spec:
        components:
          server:
            features:
            #  managementUrlFor3scale: https://3scale-admin.apps.mycluster.com

   3. Save the resource.

      This updates the syndesis custom resource. The update removes the OPENSHIFT_MANAGEMENT_URL_FOR3SCALE environment variable. This change to the syndesis custom resource triggers syndesis-operator, which is responsible for installing Fuse Online, to redeploy syndesis-server. The new default behavior is that APIs are no longer exposed for discovery in 3scale.

   Do not edit the syndesis-server DeploymentConfig object to remove the setting of the OPENSHIFT_MANAGEMENT_URL_FOR3SCALE environment variable. This does not work because syndesis-operator reverts your change. The syndesis-operator ensures that Fuse Online is deployed only and always according to the syndesis custom resource.

4. Republish any API provider integration that had discovery enabled and that was created in the project in which you just disabled discovery.

   In other words, you do not need to republish an API provider integration if you disabled discovery of that integration’s API while discovery was enabled for the project in which the API provider integration was created.

Procedure

1. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

2. Switch to the project in which Fuse Online is running. For example:

   oc project my-fuse-online-project

3. Edit the syndesis custom resource:

   1. Invoke the following command, which typically opens the resource in an editor:

      oc edit syndesis

   2. Ensure that the following lines are in the resource. Edit as needed.

      spec:
        addons:
          todo:
            enabled: true

   3. Save the resource.

      Saving this change to the syndesis custom resource triggers syndesis-operator to create a new todo pod.

Procedure

1. In the Fuse Online namespace, set the monitoring-key=middleware label by using the following command:

   oc label namespace <fuse-online-namespace> monitoring-key=middleware

2. Verify that your Fuse Online installation added the application monitoring configuration resources to the OpenShift cluster:

   1. In the OpenShift web console, go to the application-monitoring project and then open the prometheus-route URL.

   2. In the Prometheus console, go to the Status → Targets page.

      If a Syndesis target is listed, then Fuse Online is configured for monitoring and you can skip to Step 4.

      If a Syndesis target is not listed, continue to Step 3.

3. To expose Fuse Online for monitoring by a Prometheus instance that is installed in a separate OpenShift project, enable the ops add-on in the syndesis custom resource:

   1. Go to the Fuse Online namespace:

      OpenShift 4.x	OpenShift 3.11
      In the OpenShift web console, go to the Fuse Online (syndesis) project. Select Catalog > Installed Operators and then click Fuse Online Operator. Click Syndesis CRD and then click app. Click Yaml to open the yaml file in the editor.	Select Resources > Other Resources. From the dropdown menu, select the Syndesis resources type. For the app resource, click Actions and then select Edit YAML to open the yaml file in the editor.

   2. Edit the yaml file to set the Syndesis.Spec.Addons.Ops.Enable value to true by adding the follow lines:

      spec:
        addons:
          ops:
            enabled: true

   3. Save the file.

   4. Wait for the pod to restart.

      Note

      Fuse Online infrastructure resources are not available immediately after you run the install commands. You might need to wait before you can see the Fuse Online (Syndesis) targets in the Prometheus Targets page.

4. To access Prometheus:

   1. In the OpenShift console for the project where the application monitoring operator is installed, open the list of routes.
   2. Next to the prometheus-route entry, click the hostname URL to open the Prometheus console.
   3. To view a list of the alert rules configured for Fuse Online infrastructure components, click the Alerts menu item.

5. To access Grafana dashboards:

   1. In the OpenShift console for the project where the application monitoring operator is installed, open the list of routes.
   2. Next to the grafana-route entry, click the hostname URL to open the Grafana console.

   3. At the top of the Grafana console, click the dashboard selector.

      • For Fuse Online integrations, select Integration - Camel. This dashboard displays the standard metrics exposed by Apache Camel integration applications.

      • For Fuse Online infrastructure components, select one of the following infrastructure dashboards:

        Infrastructure - DB

        Displays metrics related to the Fuse Online Postgres instance.

        Infrastructure - JVM

        Displays metrics about the running JVM for the syndesis-meta or syndesis-server applications. Chose the application that you want to monitor from the Application drop down list at the top of the dashboard.

        Infrastructure - REST APIs

        Displays metrics relating to the Fuse Online infrastructure API endpoints, such as request throughput and latency. Choose the application that you want to monitor from the Application drop down list at the top of the dashboard.

6. To access Prometheus Alertmanager:

   1. In the OpenShift console for the project where the application monitoring operator is installed, open the list of routes.

   2. Next to the alertmanager-route entry, click the hostname URL to open the Alertmanager console.

      If the Fuse Online infrastructure is healthy, the default view is empty.

      If any of the infrastructure components are unhealthy, any active alerts that have been fired are listed, along with the option to silence them.

Procedure

1. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

2. Switch to the OpenShift project that is or will be running the Fuse Online environment for which you want to configure backups. For example:

   oc project my-fuse-online-project

3. Create an OpenShift secret. In the command line:

   • Specify syndesis-backup-s3 as shown in the following command format.

   • Replace the AWS variables with your AWS access key, AWS secret key, AWS region in which the bucket resides, and the name of the bucket.

     Use the following command format to create the secret:

     oc create secret generic syndesis-backup-s3 \
     --from-literal=secret-key-id="my-aws-access-key" \
     --from-literal=secret-access-key="my-aws-secret-key" \
     --from-literal=region="aws-region" \
     --from-literal=bucket-name="aws-bucket-name"

     This secret must be present when the backup job is running.

4. If Fuse Online is not yet installed, you must edit the default-cr.yml file to enable backups. See Editing the syndesis custom resource before installing Fuse Online. After Fuse Online is installed, there will be backup jobs according to the schedule that you specified in the custom resource.

   If Fuse Online is running, you must edit the syndesis custom resource:

   1. Invoke the following command, which opens the syndesis custom resource in an editor:

      oc edit syndesis

   2. Add the following under spec::

      backup:
        schedule: my-backup-interval

      Replace my-backup-interval with the desired duration between backups. To determine how to specify the interval between backups, consult the following resources:

      • cron pre-defined schedules

      • cron intervals

        Do not specify the @ sign in front of the interval. For example, to configure daily backups, the custom resource would contain something like this:

        apiVersion: syndesis.io/v1beta1
        kind: Syndesis
        metadata:
          name: app
        spec:
          backup:
            schedule: daily

5. Save the file.

   This adds a backup job to syndesis-operator.

Procedure

1. Download the desired backup file from Amazon S3. Details for doing this are in the AWS documentation for How Do I Download an Object from an S3 Bucket?

2. Extract the content of the zip file. For example, the following command line unzips the 7.6-2020-03-15-23:30:00.zip file and copies the content into the /tmp/fuse-online-backup folder:

   unzip 7.6-2020-03-15-23:30:00.zip -d /tmp/fuse-online-backup

3. Decode the Fuse Online database, for example:

   base64 -d /tmp/fuse-online-backup/syndesis-db.dump > /tmp/fuse-online-backup/syndesis-db

4. Switch to the OpenShift project that is running the new Fuse Online environment. For example, if the new Fuse Online environment is in the my-fuse-online-project, then you would invoke the following command:

   oc project my-fuse-online-project

   The remainder of this procedure assumes that you have switched to the project that contains the new Fuse Online environment.

5. Obtain the name of the database pod.

   If the restored Fuse Online environment uses the provided, internal, PostgreSQL database, invoke the following command to obtain the name of the database pod:

   oc get pods -l deploymentconfig=syndesis-db -o jsonpath='{.items[*].metadata.name}'

   If the restored Fuse Online environment uses an external database, it is assumed that you know how to obtain the name of the pod for that database.

   In the remaining commands, where you see DATABASE_POD_NAME, insert the name of the database pod for the restored Fuse Online environment.

6. Scale down the components that are accessing the database in any way.

   1. Scale down syndesis-operator so that other components can be scaled down:

      oc scale dc syndesis-operator --replicas 0

   2. Scale down the syndesis-server and syndesis-meta components:

      oc scale dc syndesis-server --replicas 0
oc scale dc syndesis-meta --replicas 0

7. Send the database backup file to the Fuse Online database pod:

   oc cp /tmp/fuse-online-backup/syndesis-db DATABASE_POD_NAME:/tmp/syndesis-db

8. Open a remote shell session in the Fuse Online database pod:

   oc rsh DATABASE_POD_NAME

9. Invoke the following commands to restore the Fuse Online database.

   If a psql command prompts for the database password, and the restored Fuse Online environment uses the provided, internal PostgreSQL database, you can find the password in the POSTGRESQL_PASSWORD environment variable in the syndesis-db deployment configuration. If the restored Fuse Online environment uses an external database, then it is assumed that you know the password.

   cd /tmp
   psql -c 'DROP database if exists syndesis_restore'
   psql -c 'CREATE database syndesis_restore'
   pg_restore -v -d syndesis_restore /tmp/syndesis-db
   psql -c "SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE datname = 'syndesis'"
   psql -c 'DROP database if exists syndesis'
   psql -c 'ALTER database syndesis_restore rename to syndesis'

   Fuse Online should now be restored. You can end the RSH session:

   exit

10. Scale up the Fuse Online components:

    oc scale dc syndesis-operator --replicas 1

    Scaling syndesis-operator to 1 should bring up the other pods that were scaled down. However, if that does not happen, you can scale them up manually:

    oc scale dc syndesis-server --replicas 1
oc scale dc syndesis-meta --replicas 1

11. The server tries to start each restored integration but you need to update connections first. Consequently, ensure that the restored integrations are not running:

    1. Obtain the Fuse Online console route:

       echo "https://$(oc get route/syndesis -o jsonpath='{.spec.host}' )"

    2. Log in into the Fuse Online console with an OpenShift user account that has permission to install Fuse Online.
    3. Display the list of integrations and ensure that all integrations are stopped. If an integration is running, stop it.

12. For each connection that has a password, you need to update the connection to have the correct password for this Fuse Online environment. The following steps show how to do this for the provided PostgresDB connection.

    1. In the OpenShift console for the project in which this restored Fuse Online environment is running, retrieve the password for the PostgresDB connection. In the syndesis-db deployment, the password is available in the environment variables.
    2. In the Fuse Online console, display the connections.
    3. Edit the PostgresDB connection.
    4. In the connection details for the PostgresDB connection, paste the retrieved password in the Password field.

13. For each integration, confirm that there are no Configuration Required indicators. If there are, edit the integration to resolve the issues. When all steps in the integration are correct, publish the integration.

    If Fuse Online keeps rolling an integration back to a Stopped state right after the Build step, delete the deployment, ensure that no configuration is required, and try publishing the integration again.

    You can safely ignore the following message if you see it in the log:

    Error performing GET request to https://syndesis-my-fuse-online-project.my-cluster-url/api/v1/metrics/integrations

Procedure

1. A cluster administrator downloads the Fuse Online package and grants permission for a user to upgrade Fuse Online in a particular project:

   1. Download the package containing the Fuse Online installation scripts from the following location:

      https://github.com/syndesisio/fuse-online-install/releases/tag/1.14

      Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.14 directory contains the scripts and supporting files for upgrading Fuse Online.

   2. Change to the directory that contains the extracted archive. For example:

      cd fuse-online-install-1.14

   3. Log in to OpenShift with a cluster administration account, for example:

      oc login -u admin -p admin

   4. Change to the OpenShift project in which Fuse Online needs to be upgraded, for example:

      oc project fuse-online-project

   5. Grant permission for upgrading Fuse Online in just this project. For example, the following command grants permission for upgrading Fuse Online to the developer user. After the cluster administrator runs this command, the developer user can upgrade Fuse Online in only this project, which is fuse-online-project, in this example:

      bash install_ocp.sh --grant developer

2. The user who was granted permission to upgrade Fuse Online performs the upgrade:

   1. Log in to OpenShift, for example:

      oc login -u developer

   2. Switch to the project in which you want to upgrade Fuse Online, for example:

      oc project fuse-online-project

   3. To check which version you are about to upgrade to, run the update script with the --version option, as follows:

      bash update_ocp.sh --version

   4. Invoke the update script as follows:

      bash update_ocp.sh

      To learn more about the script, invoke bash update_ocp.sh --help.

      During and after an infrastructure upgrade, existing integrations continue to run with the older versions of Fuse Online libraries and dependencies.

3. Upgrade Fuse Online integrations that are running as follows:

   1. In Fuse Online, select the integration that you want to upgrade.
   2. Select Edit.
   3. Select Publish to republish the integration.

   Republishing the integration forces a rebuild that uses the latest Fuse Online dependencies.

Procedure

1. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

   oc login -u developer -p developer

2. Switch to the OpenShift project that is running the Fuse Online environment that you want to uninstall. For example:

   oc project my-fuse-online-project

3. Delete Fuse Online infrastructure:

   oc delete syndesis app

4. Delete syndesis-operator DeploymentConfig and ImageStream resources:

   oc delete dc/syndesis-operator
oc delete is/syndesis-operator

Procedure

1. Log in to OpenShift with an account that has cluster administration privileges. For example:

   oc login -u admin -p admin

   While cluster administration privileges are required for only the syndesis-operator grant command, this procedure assumes that a cluster administrator is performing all steps.

2. Switch to an OpenShift project in which Fuse Online is running. You are exposing the public API in only this project. For example:

   oc project fuse-online-north

3. Grant roles to the syndesis-public-oauthproxy service account. Your OpenShift project uses this service account to run an OAuth proxy service. Specify a user account that has cluster administration privileges. For example:

   syndesis-operator grant --user developer

   This command creates and assigns a cluster role and cluster role binding to the syndesis-public-oauthproxy service account. The ClusterRoleBinding specifies the name of the OpenShift project in which you are exposing the API, which is fuse-online-north in this example:

   • ClusterRole: syndesis-auth-delegator
   • ClusterRoleBinding: syndesis-fuse-online-north-auth-delegator

4. Create a client service account and grant it permission to access the Fuse Online public API:

   1. Create an OpenShift service account with a name that you choose. For example, the following command creates the cicd-client service account:

      oc create serviceaccount cicd-client

      Commands that invoke public API endpoints use this account to access the public API. Also, you will need this service account to obtain a secret token, which must be specified in calls to API endpoints. This is described in Obtaining a secret token for calling a REST API endpoint.

   2. Grant the client service account permission to access the Fuse Online public API. If fuse-online-north is the name of the OpenShift project in which Fuse Online is installed, and if cicd-client is the name of the service account that you created for accessing the API service, then you would invoke the following command:

      oc policy add-role-to-user edit system:serviceaccount:fuse-online-north:cicd-client`

5. Edit the syndesis custom resource:

   1. Invoke the following command, which typically opens the resource in an editor:

      oc edit syndesis

   2. Edit the resource so that it enables the public API and specifies the Fuse Online environment’s public address for invoking endpoints as the setting of routeHostname. (If edits to the default-cr.yml file, which was used to install Fuse Online, enabled the public API and specified the route hostname for endpoints, you will not need to edit the resource.)

      Your cluster setup determines the public address that you need to specify. For details, see the OpenShift documentation for routes. In the following example, the route host name is valid for a minishift cluster.

      spec:
        addons:
          publicApi:
            enabled: true
            routeHostname: public-syndesis.192.168.64.63.nip.io

   3. Save (or close) the resource.

      Saving the syndesis custom resource triggers syndesis-operator, which is responsible for installing Fuse Online, to deploy the public API OAuth proxy service.

      If you did not need to edit the syndesis custom resource, then the public API OAuth proxy service has already been deployed. This is probably because publicApi was enabled and its route specified in the default-cr.yml file that was used to install Fuse Online.

Procedure

1. Obtain the names of the secret tokens for the service account that you created when you exposed the public REST API for this Fuse Online environment. For example, if cicd-client is the name of the service account, you would invoke the following command:

   oc describe serviceaccount cicd-client

   This displays a list of information about the cicd-client service account including the names of its two tokens, which looks something like this:

   Tokens:      cicd-client-token-gxb25
                cicd-client-token-gxdnv

2. Display the content of either one of the tokens. For example:

   oc describe secret cicd-client-token-gxb25

   This displays a list of information, including a Data section that displays token: followed by a long series of random characters. This is one of the service account’s two secret tokens.

3. Copy the secret token, paste it into a file, and save it.

Procedure

1. In the Fuse Online navigation panel on the left, click Integrations.
2. In the list of integrations, at the right of the entry for the integration that you want to mark, click to display a popup menu and click Manage CI/CD.

3. In the dialog that appears, do one or more of the following:

   • If the environment for which you want to mark this integration already appears, select the checkbox to the left of that environment.
   • If the environment for which you want to mark this integration is already selected, leave it selected.
   • If you need to create a label for an environment, then click Manage CI/CD, which displays a dialog for creating new environment labels. Create the label that you need, and then return to this procedure to mark the integration.

   Fuse Online applies selected environment label(s) to the integration. You can apply any number of environment labels to an integration.

4. Click Save.

Procedure

1. In Fuse Online, in the left navigation panel, click Integrations.
2. In the upper right, click Manage CI/CD.

3. On the Manage CI/CD page:

   • To create a CI/CD environment label:

     1. Click Add New.
     2. In the Add Tag Name dialog, in the Tag Name input field, enter a name for a new environment label, for example, test1.
     3. Click Save. On the Manage CI/CD page, there is a new entry for the environment label that you just added.

   • To change a CI/CD environment label:

     1. In the list of CI/CD environment labels, in the entry for the label that you want to change, click Edit.
     2. In the Edit Tag dialog, change the name as needed.
     3. Click Save to see the updated name in the list of environment labels. Fuse Online applies the updated name to every integration that is already marked with the environment label that you changed.

   • To delete a CI/CD environment label:

     1. In the list of CI/CD environment labels, in the entry for the label that you want to delete, click Remove.
     2. In the confirmation dialog, click Yes. Fuse Online deletes the environment label and also removes the deleted environment label from any integrations that have been marked with it.