Harness changes harness.io

Improvement

Now the admins can choose to give the access to Read/Edit/Delete specific workflows & pipelines to the users.

Checkout the Docs!

New

Harness users can now easily approve or reject their deployment pipelines with APIs. This will help automate the approval process and reduce the overall lead time. Users don't have to access the UI to manually approve/reject pipelines.

Checkout the docs!

Early Access

Users can now get event notifications about their deployment pipelines to any logging tool of their choice. They can set up events to be sent when the pipeline begins, completes, or pauses during execution to any webhook endpoint. This will help users gain better visibility over their entire DevOps process.

The events can also be managed with GraphQL APIs.

Feature Flag - APP_TELEMETRY

check out the docs!

A few months ago, the Harness team released the feature: Helm Charts treated like an artifact source. The user can publish a Helm Chart and trigger it based off deployment. The Helm Chart is tracked like an artifact when Harness deployed it.

The new experiences we have introduced includes:

• API support to deploy services that have Helm Charts as an Artifact Source configured.
• A streamlined experience to configure Helm Charts as the Artifact Source
• Optimized Manifest collection to fetch Helm Charts from Helm Repos for Deployment selection
• User can provide multiple manifest sources for a service

Check out the docs for API : https://docs.harness.io/article/sbvn6uwcq1-deploy-helm-charts-using-api

Docs for Deploying Helm Charts: https://docs.harness.io/article/p5om530pe0-deploy-a-helm-chart-as-an-artifact

Happy Deploying!

Improvement

Early Access

Users have multiple environments (Dev, UAT and Production) where services are deployed using Harness. Now we are helping you compare two environments and visually see what versions are services are available in each of them. This comparison is helpful to not only identify what services need to be upgraded but also very handy in trouble shooting issues. This feature is behind a feature flag and you can reach out to our customer success team for enabling it.

Feature flag name: COMPARE_SERVICE_BY_ENV

For more details, check out the docs.

Improvement

Harness takes an hour or two to cleanup the artifacts deleted at the artifact repositories. We are introducing an API to trigger the cleanup job on an ad-hoc basis.

This improves the success rate of deployments since now, the artifact deleted at source will not appear in harness while initiating the deployments.

Check out the docs

Early Access

Harness users can now provide the github webhook secret in Trigger config and only if the secret matches in github webhook and trigger, the trigger will get invoked. This improves the security of the triggers by ignoring the invokes from an inauthentic source. Even if someone get the access to the webhook somehow, it will not be able to trigger the deployments.

Feature Flag - GITHUBWEBHOOKAUTHENTICATION

Check out the Docs

New

Harness users can now provide the github webhook secret in Trigger config and only if the secret matches in github webhook and trigger, the trigger will get invoked. This improves the security of the triggers by ignoring the invokes from an inauthentic source. Even if someone get the access to the webhook somehow, it will not be able to trigger the deployments.

Check out the Docs

Early Access

Harness users now have the ability to create HashiCorp Vault Secrets Manager with reference to the HashiCorp Vault Namespace. This feature is behind the VAULT-NAMESPACE feature flag. Please reach out to Harness support to enable this feature for your account. Happy Deploying 🚀

Checkout the docs.

New

Harness has added a new permission to rollback workflows. This allows users to rollback a service to the last successfully deployed version or initiate a rollback for a running workflow even if they don't have permission to execute the workflows.

checkout the docs for more details!