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.
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:
Click the Go to Details button to access your added service instance. Otherwise, click Close to close the summary.
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.
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:
Once your environment is successfully connected, the Service Details screen also displays the following sections within the environment tabs:
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 details, OS, software, etc.) and event summary.
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:
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.
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.
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.
Access the Service Details screen and click the Add button under Environment Variables to define a new value for your environment variable.
Specify your environment variable key (e.g., ASSET_REQUEST_APPROVE_TEMPLATE_ID) and its value (e.g., activation template value: TL-262-572-051).
In case the Secured checkbox is checked, the provided value will be encrypted. Thus, this value can be used only by your extension project.
The system also enables to instantly apply values for your environment variables by clicking the Apply Change button once their values are successfully specified.
In case your task is failed, the system allows examining your failed task details, such as a task category, error message, and more. Refer to the Extension Project documentation to learn the difference between various task categories within the DevOps module.
Locate your failed task under Task Queue via your added Service Details screen. Thereafter, click on the vertical ellipsis (⋮) icon and select Details to access the Task Details screen.
Note that the system allows you to manually restart your failed task. Click the Retry button from the Task Details screen. Therefore, the system will process your selected task once again.
In case your environment is deployed in the Local mode, your logs will be generated locally. However, if your environment is running in the Cloud mode, your generated logs will be displayed within your added service details screen on Connect. Logs are used to receive detailed information about request state changes, unhandled exceptions and other events. The system allows switching logging levels as follows:
Click the Settings button in the Events section of the Service Details screen. The system prompts you to select one of the following logging levels:
Note that the system also allows utilizing the logz.io service to access logging data within the Kibana interface. Click the Open in the Logz.io button to access this service.
Once your extension project is successfully configured and your environment is deployed, the Connect platform allows examining your specified extension capabilities. Note that these capabilities are defined during the extension project bootstrap operation.
Access your added service details screen. Thereafter, click the Details button under Capabilities to review your selected capabilities.
The Subscription tab displays your selected subscription processing capabilities and subscription validation capabilities. Note that Connect displays enabled statuses for each of the fulfillment request types that are supported by your extension project.
Next, the Tier Config tab, as the name implies, provides your enabled tier request processing and tier request validation capabilities. The system also showcases enabled statues for each tier request types.
Lastly, the Product tab is used to review the product action and custom event capabilities. Refer to the Extension Project documentation in case more detailed information on any of the displayed capability is required.