User Interface

Updated: July 13, 2021

The DevOps module on the CloudBlue Connect platform is used to add and configure your services. Furthermore, this module is used for monitoring your deployment environments and accessing your logs and events. Follow the instructions below to add and successfully configure your service on the Connect platform.

Adding Services

Click the Add Service button to launch a wizard. This wizard helps users create a new service instance.

Follow the wizard steps to add a service on the Connect platform:

  1. Enter your service instance name and specify its description.
  2. Select your required product from the following list.
  3. As a result, the system generates a service instance and provides a summary.

Click the Go to Details button to access your added service instance. Otherwise, click Close to close the summary.

Service Details

Once your service is added to the DevOps module, click on your service from the provided list to access the Service Details screen.

The Service Details screen displays your selected product, specified name and specified description. Click the Edit button at the top-right corner of the screen to edit service name or your description. In addition, the vertical ellipsis () button enables users to delete their service on the Connect platform.

Deleting Services

Note that it is possible to delete a service only in case all of your environments are stopped or disconnected.

The Service Details screen enables Connect users to access Developer(Dev), Production(Prod) and Staging (Test) environments via corresponding tabs on the user interface. The system provides the following sections within each tab:

  • Environment: This section displays your environment mode (Local or Cloud) and its status (Disconnected, Connected or Stopped). Click the Edit button to configure your environment as described below. In case the Cloud mode is connected, this section also displays your deployed container instances, CPUs and memory. Furthermore, this section also provides your Git repository and links to your readme and changelog.
  • Local Access: This section is available in case the Local mode is selected. This section provides an Instance ID that is used to to process your environment queue locally. Copy the link by using the corresponding icon from this section.
  • External Events: This section provides a JWT secret that is required to forward external events to your selected environment. Show/hide or copy your JWT secret by using corresponding icons within this section.
  • Environment Variables: Specify your environment variables with this section. Click the Add button to create a new variable. In addition, import or export your variables list by using corresponding buttons in this section. Click the Edit button to change a variable from the list. Delete your variable by clicking on the vertical ellipsis () icon.
  • Tasks Queue: Use this section to examine tasks queue for your environment. For example, this queue may include pending fulfillment requests or tier configuration request that should be processed by Vendors systems. Note that in addition to processing tasks queue instances, the system also supports scheduled and rescheduled events.

Once your environment is successfully connected, the Service Details screen also displays the following sections within the environment tabs:

  • Stats: This section presents resource monitors that shows your CPU, Memory and Network utilization. Switch between your hour, day and week statistics by using the corresponding buttons in this section.
  • Capabilities: This section provides capabilities that are dynamically reported by your business logic.
  • Events: Use this section to examine and review events within your selected environment.

Furthermore, the Audit Trail tab within the Service Details screen represents a security-relevant chronological record that provides auditors with a set of service events and activities. This tab also includes event date, actors, technical details (such as browser, OS, software, etc.) and event summary.

Environment Configuration

Access the Service Details screen and click the Edit button from the Environment section to start configuring your selected environment. Therefore, the system provides a wizard that helps users with the following configuration:

1. Mode

Select either the Cloud mode or Local mode in the provided list. The Cloud mode deploy your environment to your specified Git repository, while the Local mode, as the name implies, deploys your environment locally.

Click the Next button to continue.

2. Repository

Specify your Cloud repository and authorization details in the following form. Note that this wizard step is available only in case the Cloud mode is selected.

Click Next to continue.

3. Tag

Specify your repository tag in the following form. This wizard step is available only in case the Cloud mode is selected.

Click the Save button to finalize your environment configuration.


As a result, the system provides an environment configuration summary.

Make sure that your provided summary is correct and click the Close button to close it.

Is this page helpful?
Translate with Google
Copied to clipboard