Release Update 06/01/2024

Salesforce

Centralizing the configuration of Git Path using Policy Settings

Organizations can leverage Opsera's Policy Settings to ensure consistency in the configuration of Git paths for various tools used in Salesforce workflows. This standardization reduces errors and ensures that all tools perform seamlessly in the environment.

Administrators can configure the Git Path once by utilizing the "Enforce Salesforce Repository Rules'' option to avoid manual updates each time a new Git tool is registered. For more info, read here. Note: If the repository matches, this configuration will override the Git Path that users have configured in their Git Tool Registry.

Capability to provide context-specific status updates during Salesforce Deployments

We improved status updates in the Pipeline Logs during Salesforce deployments. Users can view context-specific status such as "In Progress" or "Pending" based on the organization's load and the number of components selected for deployment. These updates are available for Salesforce Validation and Deployment steps.

Implementation of User-Initiated Access Button in Salesforce Tasks and Pipelines Wizard

Any user can now access the execution on demand in the Salesforce Tasks and Pipelines wizard by using the Access Feature button, which is available after the lock timeout in the wizard. This capability gives users additional visibility and control over their access to Salesforce wizard, enabling them to effectively manage their processes.

Previously, when an execution was locked in the wizard, access was assigned at random to a user waiting to update it. However, with the introduction of the Access Feature button, users can now initiate access rather than depending on a random assignment.

SDLC and DevSecOps

Capability to Migrate Repository from Bitbucket to GitHub Enterprise Server

Opsera provides developers with the capability to migrate repositories from Bitbucket to GitHub Enterprise Server seamlessly. This migration process involves transferring various components like Git source code, commit history, pull requests, and more from one platform to another while ensuring the integrity of the version control system is maintained.

Developers can track the progress of the migration in real-time using Opsera’s monitoring capabilities. This end-to-end visibility enables teams to stay informed about the status of the migration and address any issues that may arise during the process. For more info, read here.

Running AWS CLI Commands in Opsera Pipelines

Opsera Pipelines offer users the ability to execute AWS CLI commands within their workflows, enabling them to interact with and manage AWS resources directly through the command line interface. Users can define the specific AWS CLI commands to be executed within the Opsera pipeline, either as inline scripts, script files, or packaged scripts.

This feature streamlines the process of managing AWS services and enhances automation capabilities within pipeline configurations. For more info, read here.

Capabilities for Redshift Deployment workflows in Opsera Pipeline

Opsera Pipeline offers the below capabilities for managing Redshift deployment workflows:

• Tracking Deployment Status: Opsera Pipeline provides a detailed summary report of the Redshift deployment process, recording the success or failure status of each change set applied. The Pipeline summary report includes detailed information such as change set ID, Author name, and status. This feature allows users to effectively monitor the outcome of individual changes made to their Redshift database.

• Custom Database Tags: Users can create custom database tags in the Redshift DB changelog table during deployments. This functionality adds personalized tags to database changes, improving traceability and streamlining organization of deployment activities.

  

Capability to Build and Push Docker Images to Azure DevOps Repositories

In Opsera Pipelines, a workflow can be established for building and pushing Docker images to Azure DevOps repositories. This process involves the creation of a pipeline that builds and publishes Docker images to Azure Container Registry. During the setup of the pipeline, it is necessary to select the Azure DevOps repository and branch where the Docker images will be built and pushed.