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 it.
Check out the docs for more details!
Harness already had an option to resume a pipeline deployment from any of the previously executed stages for the failed deployments. With this feature, users can resume the pipelines for Aborted, Expired, and Rejected pipelines as well.
Please refer to our docs for more details on Resume Pipeline deployments!
With this feature, harness users have the ability to provide Http headers in key-value pairs. Earlier, we had inconsistencies when headers contained special characters (: and ,). Now the HTTP steps are much more robust and support the headers with special characters. The same is supported in HTTP templates as well.
Oftentimes, user's packaging their artifacts in a format that is compliant with their organization. This doesn't mean the underlying platform accepts that package as is. Users may need to unzip it and process it before performing the deployment. We have now enabled this functionality for PCF.
This includes artifact formats like (NuGet, tar, etc.)
Check out the docs
Harness now allows masking the values of script output variables in Shell Scripts. It's supported for both Shell script step in a workflow and from template library. The variable values will not be displayed in execution details and logs if the type is Secret. This will help avoid unintended access to the sensitive data like secrets and reduce security threats for users. For more info please check out the docs!
Shell Script Step setup
Execution Details
