Harness changes harness.io

Harness provides out of the box reporting capabilities and users can create dashboards to report key deployment metrics like deployment frequency, lead time to production, deployment duration etc using the primary and custom widgets available in custom dashboards. With this new enhancement, users can create report on deployment and instance details from the last 12 months. This will help to understand and optimize teams' devops processes.

This is currently behind a feature flag and you can reach out to Harness support for enabling this for your account. For more details check out our docs here!

Harness users can now attach and detach Tags to the resources (applications, services, environments, etc.) using GraphQL API. You also have an option to get the usages of the tags by querying for a specific or a list of tags and you are getting the details of the tags while querying any resource.

This makes it much easier to auditing if the organization's standards for Tags are being met or not and bulk updates the tags for the resources.

Check out the Docs!

Users can now see the labels alongside the data in the graphs that are created as part of custom dashboards. This improves the readability of the graphs and helps users easily visualize their deployment metrics when there is lot of data or even when presented as snapshots!

Vs

.

With this improvement, Harness users and admins can now specify delegate selectors for their artifact connectors. When specified, Harness will connect to the artifact end points only through these delegates that are part of the selectors. This helps to achieve isolation between Development/QA and Production resources. Users can now avoid connectivity from Development infrastructures (and delegate) to any Production related artifact sources.

Delegate selection is supported for Artifactory, Nexus and Docker connectors.

.

Check out the docs for more details on how delegate selectors work.

Harness provides first class support for Google Cloud Builds. You can now execute GCB builds as part of Workflow and also provide config files inline or in remote Git repos.

Feature Flag - GCB_CI_SYSTEM

Check out the Docs!

Harness now provides the details of the previously deployed artifact for a workflow where a failure is encountered and workflow is rolled back. The same details are available using context variables as well. Now the users can get the currently deployed artifact details in case of rollbacks through APIs directly.

Please refer to our docs for more details!

Harness users can now use GraphQL API to Resume a Failed, Aborted, Expired, or Rejected pipeline deployments. This makes it much easier to automate the deployments as now the users need not come to the graphical interface for resuming the pipeline deployments

Please refer to our docs for more details!

Harness integrates with Google Secrets Manager to store secrets you create in Harness. We can also reference existing secrets from the Google Secrets Manager. These secrets can be leveraged for Deployment usage!

Check out the Docs

Harness allows you to conditionally execute workflows steps or stages in the deployment pipelines with the help of skip assertions.We are now adding more visibility and providing all the variables (with the values) in the execution context for the respective steps and stages. This will help understand why the steps/stages are skipped or not during the execution of any deployment.

Devops team can now have more control on when the deployments can happen. With the new deployment freeze capability, you can set time windows during which deployments to certain environments can be restricted. Your teams can continue deploy services to Development or QA environments while you can freeze deployments for just your Production. This is currently available behind a feature flag and please reach to Harness Customer Support or your customer success team for enabling the feature flag NEW_DEPLOYMENT_FREEZE.

Check out the docs for more details!