The following new features were added to the Harness platform components:
Platform
N/A
CD
Cloud Foundry CLI v7 supported (CDP-16996). Now you can select an Enable CF CLI 7 option when creating the Harness TAS Service. If you enable Enable CF CLI 7, the Harness Delegate will use that CLI version to execute the correct set of commands. If you want to use CF CLI 7, ensure you install it on the Harness Delegate using a Delegate Profile. See Connect to Your Target Tanzu Account.
In Provision Infrastructure Using Cloudformation, in Create Stack Step, you can now define AWS CloudFormation capabilities while deploying the CloudFormation Template. Also, you can add AWS tags to the CloudFormation Stack. (CDP-17588) This will help you to create/update the stack where:
There is need to include resources that can affect permissions in your AWS account. For example, creating new AWS Identity and Access Management (IAM) users.
There is need to support macros (perform custom processing on templates). For example, include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. See: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/continuous-delivery-codepipeline-action-reference.html
Also, you can now add tags to the CloudFormation stack. This will associate Key-value pairs with this stack. AWS CloudFormation also propagates these tags to the resources created in the stack. This will help in scenarios where, say, you need to:
identify and categorize those resources.
identify your stack for purposes such as cost allocation. Ref: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-add-tags.html
The following new features were added to the Harness platform components:
Platform
N/A
CD
For K8S Apply Step, you can now Skip Harness Manifest Preprocessing Step. To do so, Select the Skip RenderingK8S manifest files Checkbox. Ensure that the Files that you Apply are Valid Manifest YAML Files. (CDP-17562)
Skip Go template rendering of Kubernetes Manifests. (CDP-17562) By default, Harness uses Go templating and a values.yaml for templating manifest files. See Use Go Templating in Kubernetes Manifests. In some cases, you might not want to use Go templating because your manifests use some other formatting. To skip rendering your manifest files using Go templating, use the Apply step instead of the default Kubernetes Workflow steps (Rollout, Canary Deployment, Stage Deployment, etc) and its Skip Rendering K8s manifest files option. See Deploy Manifests Separately using Apply Step.
CCM
N/A
CV
N/A
Issues Fixed in the Release
N/A
Component Versions
The following table lists the component versions in this release.
Name
Version
Manager
70222
Delegate
70222
Watcher
70222
Verification Service
70222
UI
69303
Learning Engine
64400
Minor Release 69716
Release Date: June 22, 2021
We're pleased to present Harness On-Premise Minor Release 69716.
The following new features were added to the Harness platform components:
Platform
N/A
CD
For any Artifact Server Edit scenario, if a User Modifies only the Artifact Server URL then a Confirmation Dialog is Shown on Clicking Submit. If the User Edits URL as well as the Username and/or Password then this Confirmation Dialog will not be shown. (CDC-13223)
The following new features were added to the Harness platform components:
Platform
Shell Script step Delegate Selector cannot select a different Delegate when InfraDef uses named in-cluster Kubernetes Delegate (CDP-17375) You can now choose to use the in-cluster Delegates in Kubernetes Workflow Shell Script steps. This will help you:
Run shell scripts on arbitrary Delegates within a Kubernetes Workflow by unchecking the Use Infra Selectors option.
Support for filter and group by options with Service Tags on the custom dashboard widgets (CDC-13028)
Users can now use the tags defined in services and workflows as filters while creating custom dashboards with Services and Workflow widgets. Tags are ways to organize and group entities. With this users can now visualize and create dashboards on the type of services and workflows are being created by the different team(s) that use Harness for deployments. See Add and Configure Custom Widgets.
Artifacts deletion for Artifactory, Jenkins, Azure Artifacts & Bamboo (CDC-13201)
We now recollect all artifacts in an artifact source when the URL in the Artifactory, Jenkins, Azure Artifacts, and Bamboo is updated. This ensures that the URL of the artifacts is up to date with the new connector URL. For example, a previous Artifactory connector URL was http://example.jfrog.io/artifactory/ and all the artifacts collected are using HTTP. If the connector URL is updated to https://example.jfrog.io/artifactory/ then all the previous and new artifacts collected would be up to date as per the new URL.
Pull latest artifacts before firing execution (CDC-13079)
You can now rely more on last collected selection for artifacts within Trigger configuration:
There were some discrepancies between latest artifact collected by Harness and latest pushed in your artifact repository. Harness collects new artifacts for given artifact stream automatically every two minutes. The discrepancy appears when in this two minutes "window" new artifact is already pushed in your repo but in the same time trigger condition is satisfied and execution is fired. This led to unexpected/previous artifact deployed. Now, before firing execution Harness will recollect all artifacts for the Services configured to use latest collected so that chances to pick older builds are minimized.
Use case: Multi service Workflow that has different artifact sources. Service A and Service B with Artifact sources A&B. The Trigger is set up On New Artifact for artifact source A with the execute options of From Triggering Artifact for Service A and Last Collected for Service B. Now artifacts for Service B will be collected again right before firing execution.
CCM
N/A
CV
N/A
Issues Fixed in the Release
Editing File Does not get Pushed from Harness to Git (DX-2507, ZD-15909)
Verification Shell script fails with Invalid request: NullPointerException (CDC-13261, ZD-15563)
Retry With Parameter, manual intervention step is not working as expected (CDC-13226, ZD-15256)
User can't add a Deployment Phase (CDC-13081, ZD-15151)
Duplicate days are appearing in Cloud Cost Management (CCM-4537, ZD-16017)
Component Versions
The following table lists the component versions in this release.
Name
Version
Manager
69413
Delegate
69413
Watcher
69413
Verification Service
69413
UI
68401
Learning Engine
64400
Minor Release 68921
Release Date: May 25, 2021
We're pleased to present Harness On-Premise Minor Release 68921.
You can now set a Delay in ECS Swap Target Groups Workflow for Blue Green Deployments (CDP-17128)
The Swap Target Groups step now has a Delay setting:
This will help you reduce incidents where non-idle connections are sent to the old service before ELB terminates the connection. This helps you ensure that all traffic has migrated to the new service before Harness begins shutting down the old service.
By default, Delay is set to 0 so it does not effect any existing Harness customer setups. See ECS Blue/Green Workflows.
For Harness Services that use Nexus and a Deployment Type that uses Group ID and Artifact ID (such as SSH), the Group ID and Artifact ID settings are changed from a drop-down to text Field. (CDC-12996)
Early Access Features List now in Product (PL-13954)
You can now see what new features are in the product but in beta or behind a feature flag:Just click Early Access in Harness.
Use CUR Report for all AWS Accounts (CE-4192)
For AWS EKS clusters, when a Harness CCM AWS connector is created, the pricing data is used from the AWS Cost and Usage Reports (AWS CUR) report instead of publicly available catalog price information. See Set Up Cost Visibility for Kubernetes Using an Existing Delegate.
Show Delegate Task ID as Part of the Execution Details (CDC-12372)
To help you identify Harness Delegate tasks in Delegate logs, the Delegate Task ID has been added to the Workflow step details in the Deployments page:
Issues Fixed in the Release
Unable to see UAT DEPLOY STAGE (CDC-12970, ZD-15026, ZD-15046)
Audit Trail does not record Triggers Deleted via Git-Sync (CDC-12878, ZD-14904)
Wrong GroupIds persisting even when repository is changed while adding nexus artifact source (CDC-12822, ZD-14775)
Rollback variables are printing as null (CDC-12725, ZD-14560)
Component Versions
The following table lists the component versions in this release.
Name
Version
Manager
68511
Delegate
68511
Watcher
68511
Verification Service
68511
UI
67500
Learning Engine
63500
Minor Release 68007
Release Date: April 6, 2021
We are pleased to present Harness On-Premise Minor Release 68007.
New Features and Enhancements
The following new features were added to the Harness platform components:
The Following Artifact Connectors Now Allow you to Select Delegate Selectors to Preference which Delegates can Perform the Task to Fetch Artifact Metadata. (CDC-11949)
You can Add a Deployment Freeze Window for your Harness Deployments. It is a Harness Governance Feature that Stops all Harness Deployments. (CDC-10994)
Custom artifact extraction for Pivotal deployments (CDP-14093)
Harness supports the most common Pivotal Web Services artifact package types. If your artifact doesn't match the supported types, you can run a script to preprocess the artifact (unzip, untar, etc).
Custom Artifact Source Feedback and Portability (CDC-11024)
Customized Failure Strategy Missing Timeout Value (CDC-11557, ZD-13269, ZD-13327)
Component Versions
The following table lists the component versions in this release.
Name
Version
Delegate
65103
Learning Engine
60100
Manager
65103
UI
64101
Verification Service
65103
Watcher
65103
Minor Release 64810
Release Date: Jan 26, 2021
We are pleased to present Harness On-Premise Minor Release 64810.
New Features and Enhancements
The following new features were added to the Harness platform components:
Support Custom Artifact Extraction for PCF (CDP-15800)
Harness supports the most common Pivotal Web Services artifact package types. If your artifact doesn't match the supported types, you can run a script to preprocess the artifact (unzip, untar, etc). Preprocessing occurs when setting up the app during deployment. See Preprocess PCF Artifacts to Match Supported Types.
Issues Fixed in the Release
Custom Dashboard is not Persisting any Widgets (DX-2313)
Component Versions
The following table lists the component versions in this release.
Name
Version
Manager
64810
Delegate
64810
Watcher
64810
Verification Service
64810
UI
63801
Learning Engine
59800
Minor Release 63902
Release Date: Jan 19, 2021
We are pleased to present Harness On-Premise Minor Release 63902.
New Features and Enhancements
The following new features were added to the Harness platform components:
AWS GovCloud and Override Default Region (CDP-14570, CDP-15915)
By default, Harness uses the us-east-1 region to test the credentials for the Cloud Provider. If you want to use an AWS GovCloud account for an AWS Cloud Provider, you can now use the Override Default Region option. See Review: AWS GovCloud and Override Default Region.
Slack/Email Notification Enhancements (CDC-11262)
Slack/Email notifications now include additional information, such as Approval expirations:See Manage Alert Notifications.
Manual Intervention Timeouts (CDC-5127)
If you select Manual Intervention for a Workflow or Workflow step's Failure Strategy, you can now enter a Timeout and Action after timeout (such as Ignore).See Define Workflow Failure Strategy.
Issues Fixed in the Release
YAML Update RBAC: Error in the Create Flow of YAML (DX-2270)
Tampered API Keys Also Work (DX-2276, ZD-13085)
Customer Git Sync Broken due to Git Diff Failed-End Commit [xx] Should be After Start Commit (DX-2224, ZD-12481)
Git -> Harness Sync Issues (CDC-11268, ZD-13066)
Editing a Service Command can Remove Variables (CDC-11251, ZD-13050)
Workflow ran Successfully but Marked as Failed (CDC-11236, ZD-13033)
Problem Creating Helm Repo (CDC-11230)
Cannot Filter by PipelineExeuctionId in ExportExecutions API (CDC-11125, ZD-12867)
Notifications not Triggered for a Resource Constraint (CDC-11123)
GraphQL Execution API Returns Error but Starts the Pipeline (CDC-10383, ZD-12373)
Email Without Body is not Delivered to Recipient (CDC-10314)
Component Versions
The following table lists the component versions in this release.
Name
Version
Manager
63902
Delegate
63902
Watcher
63902
Verification Service
63902
UI
63100
Learning Engine
58600
Minor Release 63304
Release Date: Jan 12, 2021
We are pleased to present Harness On-Premise Minor Release XXXXX.
New Features and Enhancements
The following new features were added to the Harness platform components:
New Side Nav for Harness Manager (PL-13207)
The new Harness Manager side navigation is enabled:
Harness On-Prem Kubernetes Cluster: Support for OpenShift Cluster (ONP-4)
See OpenShift Clusters in the Harness On-Prem Kubernetes Cluster setup doc.
Harness On-Prem Virtual Machine: Single and HA modes supported
There are now three modes you can select when installing Harness On-Prem Virtual Machine:
ECS Auto Scaling Attached in Last Workflow Phase (CDP-16010, CDP-15733)
ECS Auto Scaling is attached on the last Upgrade Containers step in your Workflow. For rollback, Auto scaling is attached to the old, working ECS service at the end of rollback.
Non-IIS and Docker Artifact Types Supported in IIS Service (CDP-15871)
When creating an IIS Service in Harness, you can select Other as the artifact type, and use non-IIS and Docker artifacts, such as Windows-native applications.
You can leverage Kubernetes list objects as needed without modifying your YAML for Harness. When you deploy, Harness will render the lists and show all the templated and rendered values in the log.
Use Secret Managers for Storing Terraform Plans (CDP-15354)
When you add Terraform scripts to your Terraform Infrastructure Provisioner, you can now select the Harness Secret Manager to use for storing Terraform plans.
Skip Versioning for ConfigMaps and Secrets Deployed into Kubernetes Clusters (CDP-14474)
By default, Harness versions ConfigMaps and Secrets deployed into Kubernetes clusters. Typically, to skip versioning in your deployments, you add the annotation harness.io/skip-file-for-deploy to your manifests. See Deploy Manifests Separately using Apply Step. In some cases, such as when using public manifests or Helm charts, you cannot add the annotation. Or you might have 100 manifests and you only want to skip versioning for 50 of them. Adding the annotation to 50 manifests is time-consuming.
