Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Notes - CD, March 23, 788xx #1084

Merged
merged 7 commits into from
Mar 24, 2023
Merged

Release Notes - CD, March 23, 788xx #1084

Changes from 3 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
69e3c6c
NG Release Notes Updates
roshnisarangadharan Mar 23, 2023
e9653dc
First Gen Release Notes update
roshnisarangadharan Mar 23, 2023
bc96f7d
Apply suggestions from code review
roshnisarangadharan Mar 24, 2023
20cd2df
March 24, CD RN
roshnisarangadharan Mar 24, 2023
31f1ee6
updated release version number
roshnisarangadharan Mar 24, 2023
1aea826
Updated version number
roshnisarangadharan Mar 24, 2023
4581c45
peer review
roshnisarangadharan Mar 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
144 changes: 144 additions & 0 deletions release-notes/continuous-delivery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,141 @@ Harness deploys updates progressively to different Harness SaaS clusters. You ca
Additionally, the release notes below are only for NextGen SaaS. FirstGen SaaS release notes are available [here](/docs/first-gen/firstgen-release-notes/harness-saa-s-release-notes) and Self-Managed Enterprise Edition release notes are available [here](/release-notes/self-managed-enterprise-edition).
:::

## March 23, 2023, version 788xx

### What's new

- [Azure Repo](https://developer.harness.io/docs/platform/connectors/connect-to-a-azure-repo/) is now supported as a manifest repo for Amazon Elastic Container Service (ECS) and Serverless.com Framework Lambda deployments. (CDS-54961)

When creating Amazon ECS or Serverless.com Framework Lambda deployment pipelines, you can now use Azure Repo as a manifest repo in the service definition.

- Harness now supports template input APIs (CDS-55694)

You can now use the `/templateInputs/[templateIdentifier]` API to get template inputs using the `getTemplateInputSetYaml` query parameter when creating a [pipeline template](https://developer.harness.io/docs/platform/Templates/create-pipeline-template).

For example, here's a template:
```yaml
template:
name: my_template
identifier: eqweqw
versionLabel: v1
type: StepGroup
projectIdentifier: projtest
orgIdentifier: default
tags: {}
spec:
stageType: Deployment
steps:
- step:
name: my_template
identifier: my_template
template:
templateRef: account.same_name
versionLabel: v1
delegateSelectors: <+input>

- Harness supports filtering Docker artifact tags based on regex. (CDS-53644)

You can now filter Docker artifact tags based on regex when using runtime inputs during pipeline execution.

- You can now provide an already created task definition ARN during ECS service configuration in Harness. (CDS-50112)

The task definition ARN points to an existing task created and available in the AWS cluster with the required definition. The task definition will be fetched using the task ARN provided and added to the ECS service configuration provided in the Harness ECS service **Service Definition**.

During deployment, the required task is deployed with the desired count provided in the **Service Definition**.

Go to [ECS deployment tutorial](https://developer.harness.io/docs/continuous-delivery/onboard-cd/cd-quickstarts/ecs-deployment-tutorial) for more information.

### Early access

This release does not include any early access features.

### Fixed issues

- The API call to create a global freeze window succeeds but the UI doesn't reflect the change. (CDS-55092)

If a global freeze window was inactive during the API call, it was updated and marked as disabled.

This issue is fixed. Changes are made to check the current or upcoming window to mark them as disabled during the API call.
- The commit Ids are not displayed properly when the feature flag, `OPTIMIZED_FETCH_FILE` is disabled. (CDS-55062)

Now you can see the commit Ids properly.
- Docker triggers are not working properly when regex support for tags are enabled. (CDS-54993)

The support for filtering Docker artifact tags based on regex caused a problem for Docker triggers when the regex is set to `\*`. The Docker triggers are not firing because `\*` is a wrong regex value and will not filter any builds.

This issue is now fixed by ignoring the regex value, `\*` in triggers.
- Helm deployment fails if there is no Helm chart values.yaml file in the root `charts/` directory. (CDS-54930)

Harness fails to fetch files with a no file found error when deploying Helm charts without any default values.yaml file. This issue is fixed.
- The Google Container Registry (GCR) fetch API fails with with a `404` or `400` error. (CDS-54925)

Running a cURL command for the API returned an error due to the presence of an OCI image header. This issue is fixed. The fetch APIs for Docker labels and manifest APIs on GCR now support OCI headers.
- The **Job/Folder Name** selection field in the Jenkins connector dispalys an additional drop-down list along with the first drop-down list if the jobs have child jobs associated with them. (CDS-54882)

This issues is fixed. Now, when you select a job that has child jobs, the child job options with input fields appear below the parent job.
- Trying to save a project-level Git template using a project-level Git connector at an account or organization-level returns the wrong error message: `OrgIdentifier cannot be empty for ORG scope`. (CDS-54668)

The error message is now updated to convey the error properly.
- Harness verifies if an image exists in Artifactory when fetching tags or versions of the image. (CDS-54644)

This verification is no longer needed because image verification is done automatically when fetching tags.
- Unable to resolve pipeline variables for Jenkins artifacts when used as runtime expressions. (CDS-54523)

This issue is fixed by resolving the connector Id during runtime to fetch the correct artifact path.
- When creating triggers, automatic suggestions don't appear for the expressions field in the **Pipeline Input** tab. (CDS-54500)

This issue is fixed.
- The CD Container step was not working because Harness was adding an invalid character in the default step name. (CDS-54733, ZD-40938, ZD-41170)
The [Container step](https://developer.harness.io/docs/continuous-delivery/cd-execution/cd-general-steps/container-step/) lets you run any Docker container in your Kubernetes cluster as part of your continuous deployment (CD) stage. Harness orchestrates the container in your cluster as part of your Harness deployment.
When creating a Container step, Harness was appending the step name with an `_` character. This led to an invalid container name because the step name is used to name the container.
Now, the `_` is no longer added to the container name.
- Dragging and dropping the steps of one stage to another stage generates a service propagation modal. (CDS-54340)

This issues is now fixed.
- Service inputs are retained when the service is set as an expression. (CDS-54336)

When a setting is set as an expression any fixed value inputs should be replaced with `<+input>`. This replacement was not happening. This issue is now fixed.
- Automatic suggestions don't appear for the expressions during infra provisioning in pipeline studio. (CDS-54266)

This issue is fixed. Automatic suggestions now appear and you can use them when creating pipelines and templates.
- The **Version** drop-down list for a service displays an invalid error message when the parent **Version** field in the **Artifact Details** page is left empty. (CDS-54202)

This issues is now fixed. The error message for the **Version** drop-down list is now conveys the error properly.
- Harness is unable to fetch Docker images even if the service account has proper permissions. (CDS-54085)

The tag list is limited to 1000 tags causing tag fetch failure if the tag provided was unavailable in the list. This issue is fixed now by using manifest APIs. These APIs help fetch Docker tags.
- The **Apply** step for a Helm manifest type returns an error if the file path starts with a forward slash. (CDS-54073)

This issue is now fixed by supporting file paths with or without forward slashes as a leading character.
- The error message displayed for a failed OpenShift CLI (OC) process is unclear. (CDS-54052)

This issue is fixed. The error messages for OpenShift deployments now displays proper error summary.
- The pipeline execution for a Helm subchart fails and displays an unclear error message if the subchart in a Helm chart manifest has an invalid value (for example, a whitespace) in its name. (CDS-54040)

The error message displayed during pipeline execution failure now conveys a proper error summary.
- Unable to deploy workloads when using Harness local store for native Helm deployments. (CDS-53937)

This issue is fixed by adding support for using Harness local store with native Helm deployments.
- Unable to delete a Kustomize patch entry once it is added. (CDS-53749)

A delete button is now added to allow users to delete values YAML, OpenShift params, and Kustomize patches that are no longer needed. File path validation is also done to ensure that file paths with empty strings are not saved.
- Unable to filter environments by using the search bar in the **Create or Select Existing Environment** dialog. (CDS-53713)

This issue is now fixed.
- The **Environments** section under the **Template Inputs** tab appears empty if infrastructure inputs are not required when deploying to all infrastructures. (CDS-53712)

If infrastructure inputs are not required when deploying to all infrastructure in an environment, the message is displayed under the **Environments** section.
- YAML validation succeeds even when whitespaces are added in the command flags of a Helm chart. (CDS-53708)

This issue is fixed. Command flags no longer accept empty values.
- The service information of a stage disappears when swapping two stages if the stage is propogated from the other stage. (CDS-53331)

The service details of stages appear properly now when you swap service propogated stages.
- Unable to view the Continuous Delivery (CD) module even if the account has an active CD license. (PLG-2047)

This issue is fixed.

## March 15, 2023, version 78712

### What's new
Expand Down Expand Up @@ -111,6 +246,15 @@ connector:
</TabItem1>
</Tabs1>
```
- The **App Resize** parameter support for Tanzu Application Services (TAS, formerly PCF) canary deployment strategy. (CDS-53201)

The TAS canary deployment strategy now supports adding **App Resize** steps. It is supported as a runtime parameter.

The parameters of the **App Resize** step are:
* **Name** - Deployment step name.
* **Timeout** - How long you want the Harness delegate to wait for the TAS cloud to respond to API requests before timeout.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duration that you want the Harness delegate to wait for the TAS cloud to respond to API requests before timeout.
OR
Duration that the Harness delegate should wait for the TAS cloud to respond to API requests before timeout. 

* **Total Instances** - Number or percentage of running instances you want to keep.
* **Desired Instances - Old Version** - Number or percentage of instances for the previous version of the application you want to keep. If this field is left empty, the desired instance count will be the difference between the maximum possible instance count (from the manifest or match running instances count) and the number of new application instances.

### Early access

Expand Down