Harness changelog
Harness changelog
harness.io

Inline hosts support for Target to specific hosts

 

New

 

Early Access

  

Earlier for SSH and WinRm deployments, in Select Nodes step user can choose to deploy specific hosts and choose from a list of hosts added previously in Infrastructure Definition.

Now you can specify hosts which are not present in Infrastructure Definition. Doc reference is here

User can also choose hosts which are not defined in Infrastructure Definition for SSH deployments on Start New Deployment screen with the option to target specific hosts enabled.

Doc reference is here

This is behind a feature flag: DEPLOY_TO_INLINE_HOSTS

Github Webhook Secret to be mandatory for Triggers

 

New

 

Early Access

  

Now you have an app-level setting by which you can make it mandatory for all the github triggers to contain Webhook secrets or else the invocations will fail. This adds an extra layer of security as now the admins can choose to not allow any triggers which are not containing Webhook secrets.

This is going to be behind the Feature flag - GITHUB_WEBHOOK_AUTHENTICATION

Support Rollback Provisioners after Phases enhancements

 

New

 

Early Access

  

As part of MVP we built the support for having a new option in the failure strategy as Rollback Provisioners after Phases at workflow & step level.

We are extending the same while a manual intervention is waiting for an action & for the manual rollbacks triggered by you.

This is going to be behind the same Feature flag - ROLLBACK_PROVISIONERS_AFTER_PHASES

You can refer to the docs here

Event Rules for Workflow events

 

New

 

Early Access

  

We are enhancing our Event rules which were earlier supported for only Pipeline events to now support workflow events (Workflow start, Workflow end, Workflow paused and Workflow continued) as well.

We will send these events in both cases if it’s a direct workflow execution or the workflow is executing as part of the pipeline.

This is going to be behind the same Feature flag - APP_TELEMETRY

You can refer to the docs here

[CG] RBAC Exclusion Rules

 

Early Access

 

Improvement

  

RBAC in CG now allows customers to define roles that provide permissions to users on all the applications except a few. Till now customers could select all or selective applications when scoping permissions on application but now they will also be able to select applications for exclusion. This helps in catering to scenarios where they want to have strict control over a set of sensitive / critical applications while allowing their teams to manage rest of the applications. This feature automatically includes any new application that is created in Harness in the list of allowed applications but they can be moved to excluded category by explicitly modifying the scope.

In the example below, permissions will apply to all the applications except "K8S Sample App" when "Exclude Selected" option is used

image.png

This is feature is behind FF CG_RBAC_EXCLUSION

Artifact collection is configurable

 

New

 

Early Access

 

Improvement

  

You can ow control how Harness collects artifacts using the Auto Collect Artifact option in Artifact Source. The Auto Collect Artifact option in Artifact Source allows you to enable and disable artifact collection to prevent any rate limiting issues.

image.png

Also, Harness provides the following artifact collection information which helps in getting insights into what is happening to your artifact collection

image.png

Feature Flag - ARTIFACT_COLLECTION_CONFIGURABLE

Docs - Link

Deployment Freeze Windows Enhancements

 

Improvement

 

Early Access

  

Based on the feedback received from our early adopters, we have enhanced the deployment freeze capability to support

  1. Ad-hoc windows (Users will be able to easily set up freeze windows to stop deployments for the next 2 hours while doing critical demos).

  2. Recurring windows (Easily set up freeze windows to avoid deployments from happening when the team is not around - no more weekend deployments).

  3. Override a freeze window when you need to hotfix (Super admins (heroes) will be able to make sure that mission-critical deployments happen even when there is a freeze).

  4. API Support (Now you can manage your freeze windows via APIs as well)

  5. Now you have the flexibility to have freeze windows for services as well. You can block the deployments for some specific services across your environments or to Production/Non-Production environments.

Docs

Feature Flag to be disabled - TIME_RANGE_FREEZE_GOVERNANCE

Feature Flag to be Enabled - NEW_DEPLOYMENT_FREEZE

CF Deployment Behavior

 

Early Access

 

 

User can now tweak the behavior on how Harness deploys Cloud Foundry Application for Blue-Green, Canary and Basic Deployment Types.These behavior changes include naming behavior for the deployed services, rollback for the services during a failed deployment, and adding properties to applications.

Blue-Green Deployment

Canary Deployment

Basic Deployment

Feature Flag

CF_APP_NON_VERSIONING_INACTIVE_ROLLBACK

Another functionality we introduced is PCF CLI v7 Support, so users can leverage CLI v7 commands with the CF Command Step. Harness will execute deployment on CLI v7.

CF CLI 7

Feature Flag CF_CLI7

Granular Access Control for Workflows & Pipelines CRUD

 

Improvement

 

Early Access

  

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

Checkout the Docs!

Feature Flag - WORKFLOWPIPELINEPERMISSIONBYENTITY

Publish Pipeline Events to an HTTP Endpoint

 

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, pauses or continues during execution to any webhook endpoint. This will help users gain better visibility over their entire DevOps process.

image.png

The events can also be managed with GraphQL APIs.

Feature Flag - APP_TELEMETRY

check out the docs!