Release Update 09/27/2024

SDLC

The capability allows users to pass input parameters dynamically during the execution of GitHub Actions workflows. Instead of embedding fixed values directly into the YAML configuration or requiring them to be predetermined, this capability enables users to specify these input values at runtime. Users can perform adjustments such as selecting specific environments for the workflow.

Additional Capability

Approver Name Capture for Approval Workflows

A capability has been introduced to record additional information about the user who approves each stage in the Pipeline Activity log. This offers user context in both the blueprint view and individual entries within the Pipeline Activity log for the approval gate step when it is executed.

The information recorded will encompass the approver’s name, their role, and timestamps, which will facilitate improved tracking. Currently, this functionality is available for Approvals happening via Opsera and Slack.

Access Control for Tag Creation and Management

A new level of access control has been introduced for the tag creation and management. Opsera now regulates which users have the authority to create or modify tags on the platform.

Administrators will maintain complete access to manage all tags, which includes the abilities to create, edit, and delete them. If a non-administrative user tries to engage with a tool or task that they do not own, their capability to create or modify tags will be restricted. This capability helps prevent unauthorized actions by users lacking administrative privileges.

Git Commit ID Capture for Pipeline Workflows

The git commit ID will be captured during the execution of pipeline workflows. This information can be accessed in both the Pipeline logs summary and the console logs, providing developers with better traceability and context for their deployments.

This feature is currently supported for the following types of pipeline workflows: Snyk, Git Custodian, Helm, Sentinel, Blackduck, Selenium, jmeter, junit, coverity, speedscale and terrascan.

Salesforce

Capability to Capture External Deployment information in Deployment Reports

The deployment reports will now include information on successful deployments performed through Opsera as well as those initiated outside of the platform. The external deployments are identified using the Salesforce org’s name in the report configuration.

Alongside the external deployment values, the reports will capture detailed triggering information. This includes data on what initiated the external deployment, providing context and clarity for each entry in the report. By consolidating both internal and external deployment data, organizations can gain valuable insights into their overall deployment success rates.