Harness Self-Managed Enterprise Edition Release Notes

Updated 4 days ago by Michael Cretzman

This document contains release notes for both the Harness Self-Managed Enterprise Edition editions.

For Harness SaaS Release Notes, see Harness SaaS Release Notes.

Release notes are displayed with the most recent release first.

Minor Release 75324

Release Date: June 10, 2022

We're pleased to present Harness Self-Managed Enterprise Edition Minor Release 75324.

New Features and Enhancements

The following new features were added to the Harness platform components:

Continuous Integration

  • n/a
Continuous Delivery
  • Implementation to support Exit code for Terraform Steps (CDS-36326)
    • The Terraform Plan step now outputs the detailedExitCode output variable. This detailed exit code is from Terraform plan (https://www.terraform.io/cli/commands/plan) and you can use this with other steps in the pipeline.
    • Info on detailed-exit-code:
      • -detailed-exitcode - Returns a detailed exit code when the command exits. When provided, this argument changes the exit codes and their meanings to provide more granular information about what the resulting plan contains:
        • 0 = Succeeded with empty diff (no changes)
        • 1 = Error
        • 2 = Succeeded with non-empty diff (changes present)
Cloud Cost Management
  • Add CloudProvider GroupBy option (CCM-7543)
    • Now user can group based on cloud provider.
  • You can choose to show/hide Unallocated cost and other columns in the Perspective's chart section. (CCM-7254)
Feature Flags
  • n/a
Service Reliability Management and Verification
  • n/a
Security Testing Orchestration
  • n/a
Chaos Engineering
  • n/a
Platform and Delegate
  • Improve Delegate tokens logic. (DEL-3998)

Issues Fixed in the Release

  • Negative Value Validation required at backend for notification-rule/{identifier} api (SRM-10682)
    • added NULL checks
  • GCP Metric Verify Step: Seeing null pointer exception in execution logs for GCP metric health source (SRM-10674)
    • Fixed a null pointer exception in data collection for verify step.
  • Manual intervention timeouts not being respected, pipelines waiting indefinitely (SRM-10656)
    • Resolving Verify step bug
  • Notifications for MonitoredService are triggered even when analysis is OFF (SRM-10652)
    • Notifications are triggered even when analysis is OFF
  • Add exception if a diff NotificationRuleType is added into a different Entity (SRM-10632)
    • Add exception if a diff NotificationRuleType is added into a different Entity
  • Two APIs are failing in Verify Step for custom mapped health source (SRM-10631)
    • added NULL checks
  • CV step is getting stuck and marked as expired (SRM-10551, ZD-30562)
    • Show exception to users when save fails for metric data collection.
  • CloudWatch verification is not happening although we see configured cpu metric is being returned for both(current and previous) canary pod (SRM-10276, ZD-30292)
    • Fixed a bug in cloudwatch EC2 timeseries analysis which was causing analysis to finish without any actual analysis.
  • Not able to delete service account at project level (PL-25432)
  • Project deletion showing extra warning message. (PL-25337)
    • In case no project was saved in PreferenceFramework (because it's disabled currently), DeleteProject was throwing an error as it was trying to access an 'undefined' project
  • If same entity is being sent twice then reference framework doesn't save any references (PL-25264)
    • Earlier duplicate Redis events (like referring to a connector in 2 stages of the same pipeline) was giving a bulk update exception, which lead to none of the instances being stored. Now we are checking for duplicates and storing only one instance
  • Error message is cut (PL-25033)
    • Fixed CSS rule to wrap words correctly and also honor white-spaces from message received from backend.
  • Secrets Selection Widget issue when a random page selected (PL-23978)
    • Replaced numbers with previous and next buttons
  • UI does not redirect back to Login when feature-flags API fails with NOT_WHITELISTED_IP error (PL-23816)
    • Added a global check to redirect User to login page when IP is not whitelisted
  • Applied InputSets are not reflecting in triggers (PIE-3860)
  • Wait till connector load before loading Manifest details (PIE-3816)
    • Added callback to get `isLoadingFinish` for status of API
  • CI builds with approval stages are being displayed in the CD deployments (PIE-3811)
  • Cypress - Env Group Create (PIE-3805)
    • Cypress test for env group after request update was not updated. This has been updated with the new URI
  • Remove Formik and FormikForm From DeployServiceSpecifications (PIE-3777)
    • Formik wrapper removed
  • Run Pipeline Form run button is disabled (PIE-3776)
  • New Pipeline Studio fixes (PIE-3761)
    • Fixed new pipeline studio bugs and alignment issues
  • Execution Strategy list not visible (PIE-3756)
    • Added default strategy as fallback
  • Pipeline Execution Crashing (PIE-3744)
  • Unable to add step template in pipeline studio (PIE-3724)
  • Error log message enhancement in UI for timeout exception or short connectivity blip (PIE-3719, ZD-30582)
  • Issue on UI on most active service widget when "byInstances" is chosen (PIE-3563)
    • 1. Added some width to text area
    • 2. formatted the text - ( 39080880 --> 39.08M)
    • 3. Added tooltip on hover to show actual number
  • UI Values in drop down box is hidden (PIE-2699)
    • Found that this was caused by the restriction applied on popovers by their parent element. This was solved by creating a React portal
  • Flag Save Button UI Bug - Save never appears completely to click (FFM-3447)
    • Trial banners no longer cut off `Save` and `Cancel` buttons in Target Rules page
  • delegateTokenName field causing Incompatibility with manager latest and delegate older version (DEL-4189)
  • Tags are not removed from the textbox even after clicking the remove button (DEL-4046)
    • Fix removal issue in the Delegate setup form. Earlier, tags and descriptions values were not removed properly.
  • TI: Test was not selected despite being in the relations table (CI-4579)
  • Send proper error messages during GitHub connector validation (CI-4561)
    • Added cases for particular exceptions.
  • Revert CI manager addon version to 1.14.0 for patch release (CI-4520)
  • Pipeline failed with error message (CI-4515)
    • Added additional logging.
  • Unable to add an annotation to build stage pipeline (CI-4481, ZD-30865)
    • Users will be able to create git enabled pipeline without seeing an error message for Volumes
  • CI not parsing Junit tests (CI-4462)
  • Changed Files filter does not work for pull request event triggers (CI-4456, ZD-30742)
    • Fixed backend bug. No change on customer side.
  • When building a PR ONLY the actually base branch name is shown (CI-4266)
    • The issue has been resolved and will go live with next release. Correct information will be shown on UI now.
  • fix: Harness Git Experience is enabled text (CDS-38374)
    • Fixed UI text to be clearer.
  • Harness Home page not show descriptive browser tab titles (CDS-38222)
  • Trigger update failing with unclear error (CDS-38107, ZD-30629)
    • Updated error by specifying exact name of variable
  • Prevent ExecutionStrategyYaml call when no serviceDefinition (fix cypress test) (CDS-38099)
    • Updated the test flow to retry after page load
  • Artifacts info is recorded incorrectly when there is a skipped stage (having no artifact) followed by a deploy stage having an artifact (CDS-38097)
    • We have rewritten the CDC Handler for service_infra table,such that the service details are populated appropriately when stages(having no artifact deployed) are skipped.
  • Approval Email Link (CDS-37798, ZD-30308)
    • Used returnURL from sessionStorage if not found in urlParams. Return URL will now be honored even on 2FA & when returning from SSO page
  • Step group yaml schema is not correct when we add selectors (CDS-37733)
  • When user saves a service in the YAML Editor, it doesn't show up in visual (CDS-37526)
    • Exposed services and environment pages, with some restrictions on respective pages i.e. only lists and adding/editing functionality will be available
  • Charts miss Y and X Axis text (CDS-37482)
    • Added X & Y axis labels
  • On manifest trigger YAML has spec and store info missing when the trigger is created via UI (CDS-37140)
    • Displayed store info under source for selected Manifest in trigger
  • Harness doesn't remember time filter selection (CDS-36473)
    • Time filters are now saved for the current session
  • Error message needs to be improved - Blank error message when the version is missing (CDS-36320)
  • Service Dashboard needs to contain artifact details (CDS-35582)
    • Environment Deployment widget will includes the custom artifacts as well.
  • Parallel Stage Pipeline Change Inject Stage (CDS-34422)
    • Added condition for displaying correct yaml for Triggers when single stage was moved to parallel stage in pipeline studio

Minor Release 75281

Important information regarding certificates and Delegate upgrade to OpenJDK 11

As part of our migration to OpenJDK 11, Delegates will download OpenJDK 11 and get started with it instead of the previous OpenJDK 8 that was used. This means that Delegates will have Java installed on a different path. Any user actions which modify or use older Java versions would be affected. Some of the most common scenarios include adding certificates to the default Java keystore and running additional Java applications using Delegates installed Java (e.g. from a profile or init script).

See Information regarding certificates and Delegate upgrade to OpenJDK 11.

Release Date: May 31, 2022

We're pleased to present Harness On-Premise Minor Release 75281.

New Features and Enhancements

The following new features were added to the Harness platform components:

Feature Flags
  • Enabled Advanced tab in all pipeline steps in the Feature Flags Pipeline Studio (FFM-3324).
Continuous Integration
  • Support runtime input for Codebase configuration now supports runtime inputs. (CI-3648)
Continuous Deployment
  • Changed return type of an newly introduced API endpoint to be aligned with already existing APIs, no real effect on API output. (CDS-36721)
Cloud Cost Management
  • You can now create up to 1000 perspectives in Cloud Cost Management. This will help you:
    • Create more detailed customer perspectives to slice and dice data.
    • Ensure every CCM user has access to their own perspective with cost data most relevant to them. (CCM-7501)
  • Workload Recommendation URLs now include Buffer, QoS State, Cost/Performance optimized, and Timeframe. Customers can now share the recommendations URL with the state maintained. (CCM-6867)

Issues Fixed in This Release

  • When we update SLO it doesn't show recalculated value. (SRM-10266)
  • YAML order of metric threshold for verify step is fixed. Before the fix It was inconsistent in some cases. (RM-10249, ZD-29515)
  • Verification Step issue with Prometheus: Step would stall after step TTL and required manual intervention. Users should now be able to proceed with the workflow. (SRM-10098, ZD-29886)
  • Trial expired banner has missing text. (PLG-1032)
  • PLG - CD Community Edition - Disable all licenses but Community Edition (PLG-705)
  • With this ticket we have fixed the following in NG Variables feature (currently behind FF):
    • Pagination icons should not be hidden on default page view.
    • Header should be fixed and page contents should be moveable.
    • Added popover for description (on hover).
    • Edit variable window should have title - Edit Variable.
    • Renamed Variable to Variables in Access control page. (PL-25122)
  • Due to preference framework, gitSyncAPI started using Org/Project from saved preferences. Due to this, gitFilters were visible on account-level page as well, which was not the intended behavior. Re-instated the gitSync API to use Org/Project from path only. (PL-25102)
  • Access to "USER" scope is not available in the current context. (PL-25097)
  • Script to tag JIRAs was misspelled and hence not found when tried to be executed. The script-name spelling is fixed now. (PL-25071)
  • In SCIM group identifier, names '.' will be replaced by '_'. (PL-24987, ZD-30279)
  • Now, read-only HashiCorp Secret Manager cannot be set as default secrets manager (PL-24810)
  • From now on if we delete an org, all the connectors in that org scope gets deleted. (PL-24786)
  • Previously, a red error message appeared at the top of the screen with the message: Account id is not marked in the request. Now, users can disable MFA in their NG user profile. (PL-24751, ZD-29833, ZD-29970)
  • An error is shown in The YAML editor shows an error if a user changes the Connector Id while updating a Connector via YAML mode. (PL-24273)
  • Fixed UX issues when checking Git details for an input-set/pipeline. (PL-24226)
  • SSH credentials with simple username password will not fail after this change. (PL-23956)
  • We have fixed a bug where View Permission link for Secret Managers in NG wasn't taking to NG Docs. Steps to verify:
    • Create AWS KMS SM ( any other SM).
    • Enter wrong credentials.
    • Test Connection screen should have view permission link.
    • Click on view permission --> Should take you to specified link in NG Docs. (PL-22352)
  • Filter name is not being displayed. Added code to fix this issue. (PL-21463)
  • Fixed issue with variable data not populating in Pipeline Studio > service tab. (PIE-3752)
  • Updated the webpack shared module dependency for Harness UI core. (PIE-3732
  • Fixed OPA dialog on policy evaluation. (PIE-3660)
  • Service variables didn't show runtime input/expression option in Pipeline variables screen. Allowable multitype was passed as []. (PIE-3732)
  • Fixed incorrect alignment of infrastructure block in Variables panel (PIE-3624)
  • Cannot read properties of undefined object due to Javascript error. (PIE-3605)
  • Cypress deletion script changes. Check for file existence before deletion added. (PIE-3578)
  • UI change: "Previous" and "Next" buttons in Pipeline Studio should be "Back" and "Continue." (PIE-3576)
  • UI issue: Unable to run Pipelines. Fixed the issue by passing correct Git details. (PIE-3572 30160)
  • UI issue: Pipeline Canvas cypress steps tests skipped due to timeout. (PIE-3544)
  • UI Issues with selective stage executions. Optimized stage selection in the form. (PIE-3514)
  • Fixed the height of filter addition section and updated filters list height based on remaining spaces. (PIE-3488, ZD-29720)
  • Added a min width of 1100px for the pipeline studio page. (PIE-3108)
  • If there are multiple stages, and if a stage failed with a rollback failure strategy that executes rollback steps, but after it the next stages will continue. The next stages will execute or get skipped based on their when condition, which was not working earlier only if previous Stage failed with rollback failure strategy. (PIE-2338, ZD-30753)
  • Cosmetic change for skipped stages - background color of node. (PIE-2172)
  • You can now see your Target name in bold before confirming it to be deleted. (FFM-3221)
  • Fixed the regression of not honoring Delegate selectors due to Jackson library upgrade. (DEL-4048, ZD-30610, ZD-30637, ZD-30772)
  • Introduced caching for ng secrets in manager, which will allow us to re-use cached secrets which are being used frequently. Hence will reduce the manager's processing time. (DEL-3957, ZD-30225)
  • Configure correct paths to built-in client tools that are being used by Delegate. (DEL-3784, ZD-29697, ZD-29727)
  • Delegate resource will appear in multi-select filter and module column missing icons for type Delegate in Audit Trail data table. (DEL-3754)
  • Alignment issue of the instances column in delegate listing is fixed. (DEL-3570)
  • Fixed incorrect pagination value issue in delegate tokens listing. (DEL-3527)
  • Removed text referencing healthCheckpointEndpoint from troubleshoot guide (DEL-3485, ZD-28279)
  • Fixed API logic to calculate Delegate connections. (DEL-3200)
  • Now you can create Parallel Stage Pipeline templates. Also some miscellaneous bugs were fixed. (CI-4436)
  • Before this fix, the active committer count for enterprise users counts one user who worked on different projects multiple times, now it does not. (CI-4413)
  • Pipeline with Codebase Connector as a runtime input was showing loading ... when user selects connector on Run Pipeline form. Now it is fixed. (CI-4408)
  • CI Build is not triggering when opening a PR. Logs added as an intermittent fix. (CI-4405)
  • Fix CI and Orchestration component tests failed in master. (CI-4357)
  • Added validation on backend to fix the case where build is empty string. (CI-4352)
  • Trim account name and namespace in BE. (CI-4345, ZD-30263)
  • CIE - Git Connector for Azure Failing intermittently. Added retry and increased network timeout. There was a communication issue between the Delegate and Azure. (CI-4331, ZD-29732)
  • Allowed values in runtime inputs are not set properly in CI. Customers should now be able to see a dropdown with allowed values specified for a field set as runtime input and select a value from the dropdown. (CI-4273)
  • Fixed the immediate issue along with automation addition. (CI-4258)
  • Assign automount Service Token to true when the user selects Kubernetes as the Infrastructure Type. (CI-4056)
  • The UI now fetches updated summary when the user clicks on different nodes. It also preselects the Stage when user switches to the Tests tab. (CI-4023)
  • Pipeline Triggers do not auto-create Webhooks. Fixed auto-webhook registration case with Harness platform. (CI-3959)
  • Customers will not be able to specify expressions for output variables. (CI-3950)
  • Handle all variables (optional/required) in variable creator according to new framework for all the steps. Support Variable V2 API. CI-3928
  • Added support for runtime input to pool name. Also added a new attribute pool_name to replace identifier, which is deprecated with this change. (CI-3416)
  • Issue: After last deployment, validation for variables having yes/no as allowed values started to fail saying value doesn't exist in the allowed values list. This started happening because yes/no was being treated as boolean rather than string (as per yaml specification: https://yaml.org/type/bool.html), hence converting these to true/false and failing the allowed values validation.
  • This was fixed after treating all the input values as String. (CDS-37478, ZD-30730)
  • Timeout for Azure connector connection check around 10 minutes. (CDS-37260)
  • Propagate from Stage template does not show up the Artifact and manifest scetion when override checkbox is checked. Fetching deployment type from template details to render manifests and artifacts section (CDS-37143)
  • Added an extra "Deployments" tag that shows data for all instances including custom deployments. (CDS-37138)
  • Intermittent issue fixed by drilling deployment type properties down from parent component. (CDS-36997)
  • Hotfix for Arfifactory Docker in NG. (CDS-36994)
  • Do not show ex strategies for Serverless and show default deploy step. (CDS-36983)
  • Added a fix to honor Git repo and branch while selecting a Pipeline template in Pipeline Studio. (CDS-36960)
  • Under Infra tab, Google Kubernetes Engine should be selected upon clicking on that tile. Fixed by using already selected infra as initial values when component gets rendered (CDS-36887)
  • On new artifact and manifest triggers not working for a Pipeline created from template. Added a fix for artifacts and manifests trigger to work with Pipeline using templates. (CDS-36813)
  • Fixed issue where the "Invalid Feature" banner appears on CD pages. (CDS-36797)
  • Docker Tags will now be listed for Account level and Org level templates. (CDS-36650)
  • "Failed to Fetch" is displayed in the Template page when user does not have permission for the Org/Project. Added relevant error message. CDS-36540
  • Number of failures is off. Temporarily hiding the failure counts. CDS-36451
  • Tooltip when manually entering an Artifact doesn't show anything. Manually enter experience not clear for tags. (CDS-36079)
  • NG Harness Approvals - UI issues with User group field as expression. Revising the user input to remove empty strings. (CDS-35995)
  • Service Dashboard needs to contain artifact details. Environment Deployment widget will includes the custom artifacts as well. (CDS-35582)
  • Delegate throwing too many redirects when running the http command. (CDS-34768)
  • On groupBy businessMapping, we are not getting the correct data because we are storing accountNames along with accountIds while saving business mapping. We removed the accountNames while saving and appended accountNames in case of get/list request. (CCM-7518)

Minor Release 74969

Release Date: May 11, 2022

We're pleased to present Harness Self-Managed Enterprise Edition Minor Release 74969.

New Features and Enhancements

The following new features are added to the Harness Self-Managed Enterprise Edition components:

  • Detailed YAML Snippets for User Group audits have been added with this release. (PL-23573)
  • You can now update users' details using service tokens. This enables you to update the details of a specific user in the Account using a Service API Key that has manage user permissions for that user. (PL-23163)
  • There is now validation for feature flag toggling. If you don't have an existing environment, you will now see an error message appearing as a tooltip informing you that you are unable to toggle your feature flag(s). The toggle will be disabled until an environment is created. (FFM-2470)
  • Delegate tokens are used by Harness to encrypt communication between Harness Delegates and the Harness Manager. By default, when a new Harness account is created, all Harness Delegates in that account include the same token. You can now use APIKeys for Delegate NG Token management.
    See the Delegate Token Resource API docs. (DEL-3609)
  • You can now view events associated with Delegates on the Audit Trail page. With Audit Trail in Harness, you can view and track changes made to your Harness resources within your Harness account. Audit events are registered for Delegate creation, Delegate deletion, and Delegate group deletion. No event is registered for Delegate update. For each event record, this view shows the following: (DEL-3377)
    • Date and time (Time).
    • The user who made the change (User).
    • Action by the user like create, update, delete.
    • Harness entity affected (Resource).
    • Organization corresponding to the affected entity.
    • Project corresponding to the affected entity.
    • Module corresponding to the affected entity.
    • Event Summary with YAML difference.
  • OrgIdentifier and ProjectIdentifier have been removed from Delegate YAML. Also, it is now mandatory to pass the Delegate token name while downloading an NG Delegate YAML. The token used by the Delegate will be used to extract the correct OrgIdentifier and ProjectIdentifier. (DEL-3184)
  • You can provide JAVA OPTS for Delegates to override Java properties for things like setting up key stores for TLS verification. This option was previously available for both Delegate and Watcher. We are breaking the variable for Delegate and Watcher with this release. The current JAVA OPTS variable will continue to function, but if you want to set it up for Watcher, you must provide WATCHER JAVA OPTS as an environment variable. This has advantages such as monitoring the Watcher and Delegate separately with APM agents. (DEL-3040)
  • The Get GCP Clusters API is hidden by the Open API Specification. (CDS-35459)
  • You can now use Custom Artifact with a fixed value in your deployments. This will help you to:
    • Use custom value for artifact version and reference in your steps using <+artifact.version> or <artifacts.sidecars.id.version> and allow to track what version has been deployed
    • Pass any artifact version from your CI stage to CD stage without the need to rely on existing or supported artifact server.
      This feature is available behind the Feature Flag CUSTOM_ARTIFACT_NG. (CDS-35216)
  • You can now use a GCP Connector when selecting Infrastructure for Kubernetes deployments. You will be able to use the GKE Workload identity when inheriting credentials from a Delegate. (CDS-7363)
  • You can now filter and Group By Perspectives based on the Cluster Type. Perspectives allow you to group your resources in ways that are more meaningful to your business needs. It provides a unified view of your cloud cost data across the cloud environment. (CCM-7259)
  • You can now use the Hide Progress Page toggle to enable or disable the Progress Page for an AutoStopping Rule for a Kubernetes cluster. (CCM-7206)
  • You can now view Kubernetes Connector details, for Kubernetes AutoStopping Rules, on Summary of Rules. (CCM-5834)
  • Workload Recommendations now include the ability to
    • Select Kubernetes Quality of Service (QoS) between "Burstable" and "Guaranteed."
    • Set a buffer (%) for the request and limit beyond the recommendation based on historical usage requirements for the workload. (CCM-5464)

Issues Fixed​

  • Fixed UI issue in Monitored Services dashboard. (SRM-9882)
  • For the Access control service to function, identifier annotations must be added. The Access Control service was blocking the Logs endpoint of the SLO and Monitored Service. (SRM-9848)​
  • CVNGLogDTO subtypes are added in the API response. (SRM-9829)​
  • Added fallback scenario to handle missing manager version headers in verification service.​ (SRM-9808, ZD-28900)
  • Service Health analysis wasn't happening for GCP Logs. State machines are set to ignore, and the next one is selected for LM. (SRM-9529)​
  • We started displaying better error message on GCP log onboarding.​ (SRM-9202)
  • Fixed the custom threshold issue when multiple thresholds are defined for a single metric for workflow verify state.​ (SRM-3680)
  • Fixed issue where the Service Instance isn't displaying count on subscription for CD​. (PLG-915)
  • Fixed typo in Subscription Overview UI. (PLG-810)
  • Fixed an issue where APIs were returning 401 due to UI Client sending an expired token.​ (PL-24587)
  • Fixed an issue where editing or opening a template in the Template Library returned 400s.​ (PL-24555)
  • SAML authorization field now allows special characters so now group names can use the format DN=ABC,DN=CDE,OU=xyx.​ (PL-24524)
  • Pipeline YAML was throwing an Invalid shell script error when saving the Pipeline. (PL-24510, ZD-29539, ZD-29760)​
  • Fixed a UI issue in the User Groups table: text for role bindings is hard to read due to colored highlighting. (PL-24500)
  • The webhook registration in Bitbucket was failing when an SSH URL was being used. This automatic webhook registration issue is fixed in this release. (PL-24326, ZD-29216)​
  • When switching accounts, from Prod-1 to Prod-2 for example, the UI resources were not getting reloaded to point to Prod-2. (PL-24067)​
  • Fixed an issue where creating a Connector using APIs returned 500.​ (PL-23979)
  • Fixed an issue where saving a Pipeline resulted in an error message.​ (PL-23931, ZD-28901)
  • Fixed issue in Connector Overview: When back button was pressed, the data from the previous step was not being retained.​ (PL-23760)
  • UI fix for overflowing long git errors​ (PL-23624)
  • Fixed an issue with User Group when User got deleted at account level. (PL-23109, ZD-27589, 29865)
  • Fixed issue with Group Authorization sync when logging via non-default account. (PL-23033, ZD-27589)
  • Added a check in GitContextForm to not retail default branch on branch change​. (PL-21504)
  • Connector Health Status was not getting refreshed after modifying the Connector parameters. (PL-21445)​
  • Branch wasn't passed to refetch handler, so refetch was working as without git. That could handle only default branches. Now it's fixed as we are passing the branch and repo information down the chain.​ (PL-21426)
  • Showing error in a Popup when user tries to delete a connector which is referenced by other entities​. (PL-21099)
  • Improvements to error messages. (PL-20356)​
  • Incorrect payload was sent when no runtime input was present​. (PIE-3523)
  • Updated UI to show error message when a user clicks Abort repeatedly while the back-end abort is still in progress.​ (PIE-3471)
  • Fixed UI issue: Report Paths not rendering when at least one value in the list is an expression in Templates Input view. Reverts to previous logic for reporting mixed list input for expressions and fixed values. Added special handling for new use cases for expression list input. ​(PIE-3456)
  • The Run Pipeline form wasn't considering values from the YAML view. (PIE-3453)
  • The Manifest submission modal wasn't working as expected. (PIE-3394)​
  • Fixed a "Something went wrong" error that appeared when a user navigated to a specific Stage due to missing null checks.​ (PIE-3360)
  • Fixed Input Set issues with a Pipeline using Stage Templates.​ (PIE-3350)
  • Resolved issues with disabling of Run Button with respect to input sets and incomplete form.​ (PIE-3349)
  • Pipeline was getting saved even without configuring any Stage. A schema constraint has now been added, which mandates that a Pipeline should at least have one stage configured; otherwise, the schema validation fails and the Pipeline won't be saved. (PIE-3315)​
  • Reset the zoom level and set the canvas to start when the user selects the different stage in the execution view​. (PIE-3302)
  • Fixed issue in which /pipelines/execution/summary gets cancelled during search results in error message. (PIE-3287)
  • Fixed an issue in which NPE displayed when there was an error (due to invalid input) followed by a user attempting to fill the timeout field. (PIE-3268)
  • Fixed an issue with Input Sets not populating fields with error Uncaught (in promise) TypeError: Cannot read properties of undefined (reading ‘sidecars’).​ (PIE-3250, ZD-28984)
  • Fixed an issue that occurred when user tried to save the input set after updating Pipeline with more runtime input fields: the input set couldn't be saved and Harness would throw an error. (PIE-3247)
  • Receiving failure email notification for successful approval Pipelines. (PIE-3246, ZD-28991, ZD-29242)
  • ​Fixed an issue where, when tests were triggered using webhooks, the Pipeline could not re-trigger the failed ones. (PIE-3238)
  • Fixed a UI issue where the wrong icon appeared for Canary deployments.​ (PIE-3235)
  • Fixed error message while saving a newly created pipeline without any stage/step​. (PIE-3233)
  • Filtered out already synced entities during full Git Sync for Pipeline input sets and templates​. (PIE-3212, ZD-28724)
  • Fixed issue where CI Codebase form re-rendered on first click on any radio button branch/tag/PR. (PIE-3194)
  • Inputs Tab - Execution View - Payload should be Read Only. (PIE-3149)
  • Zoom out option for payload in policy step added​. (PIE-3147)
  • Added runtime and expression support for policy sets in policy step​ (PIE-3146)
  • Added runtime annotation to policy sets list​. (PIE-3145)
  • Design fixes to render longer policy set names in Pipeline Studio (PIE-3144)
  • Routing to individual policy and policy set​. (PIE-3137)
  • Improved error message for Policy step Evaluation failures​ (PIE-3136)
  • Added missing placeholders in Execution step editors in Dynamics provisioning in Infrastructure tab​. (PIE-3049)
  • Run validation function to recheck the state of the form and form errors.​ (PIE-2738)
  • Fixed variable screen user abort error by increasing debounce duration and fixed error message CSS. (PIE-2732)
  • Fixed issue where data is not populating with the last input set applied. (PIE-2459)
  • Fixed UI issue with the feature flags being displayed​. (FFM-2204)
  • Fixed issue where tags are not removed from the textbox even after clicking the remove button. (DEL-4046)
  • Delegate registration was failing when the number of characters in the hostname was more than 64. (DEL-3783, ZD-29691)​
  • Changing the tags of the YAML after the Delegates were created wasn't changing the Tag. (DEL-3751)​
  • Fixed issue where builds stopped working due to lack of delegates / bad state. (DEL-3750, ZD-29493)
  • Fixed issue where Delegates weren't available during Pipeline execution. (DEL-3661, ZD-27753, ZD-29167, ZD-29282)​
  • Immutable Delegate was generating repeated logs which was flooding out the useful logs. (DEL-3645, ZD-29125)​
  • Fixed issue where builds hang at Git Clone. (DEL-3600, ZD-28989)
  • Fixed issue where wrong delegate token name was getting saved in Delegate collection​. (DEL-3578)
  • Fixed issue where NextGen Jfrog step couldn't get authorization. (CI-4262, ZD-29409)
  • Source Code Manager (SCM) was throwing an error message when the certificate file wasn't specified. A Harness Source Code Manager (SCM) contains your personal account for a Git provider such as GitHub or AWS CodeCommit. (CI-4057)​
  • Resolved issue where Pipeline execution fails during building/pushing docker image step. (CI-4042, ZD-29230)
  • Key for Priority Class was using priorityClassName instead of priorityClass. (CI-4038)​
  • Fixed issue where versioning wasn't working for Docker Image. (CI-4027, ZD-29230)
  • RunAsUser was not accepting numbers. With this fix, now numbers and strings both will be accepted. (CI-4009)​
  • Customers should be able to provide fixed values for report paths and output variables field in Run/Run Tests step templates.​ (CI-3953)
  • Customers should now be able to set fixed values for "sourcePaths" in Save Cache to S3/GCS template-linked step.​ (CI-3943)
  • Customers should be able to specify output variables in Run/Run Tests steps as key value pairs with “name” as the key.​ (CI-3927)
  • Fixed issue where Trigger webhook curl command had parsing error. (CI-3906)
  • Customers will now we able to see template inputs where a field is set as runtime input with allowed values.​ (CI-3905)
  • The Ungrouped data will show correct information for the scenario when pages is greater than 20. Previously it was inaccurate when result pages > 20​. (CI-3899)
  • Pipelines were failing and throwing an error 'Could not resolve outcome with name 'podDetailsOutcome'' when using an encrypted Username. (CI-3895, ZD-29004)
  • Pipeline execution was marked successful even when Artifact was not uploaded to S3 bucket. (CI-3875, ZD-28610)​
  • Implemented a fix so that users can see the page that says No Test Results if this is the case​. (CI-3867)
  • You will now only see the purple container (Call to action) when the user doesn't have a TI step (Run Test step) in their pipeline​. (CI-3847)
  • When two Triggers with the same ID were used to initiate two different Pipeline executions, activation in the second Pipeline was being caused by the Trigger created for the first Pipeline, unless refreshed. (CI-3745)
  • Pipeline with Steps that had a CPU limitation set by an expression wasn't running. (CI-3717, ZD-28479)​
  • Users will now be able to scroll to view their Pipeline YAML in the Trigger Details page​. (CI-3704)
  • Git URL https://www.github.com/wings-software/jhttp wasn't working. (CI-3604)​
  • Updated the error message in case CI stage fails to create pod secrets. (CI-3602)
  • The Pipeline execution was failing due to a PR trigger failure with the following error message:
    Failed while requesting Pipeline Execution through Trigger: Error creating Plan: Unexpected plan creation error: Could not read json provided for the fqn: pipeline/stages/[0]/stage/spec/execution. Could not read json provided for the fqn: pipeline/stages/[0]/stage/spec/execution
    (CI-3598, ZD-28421, ZD-28586)​
  • Harness now updates the step status on SIGTERM. Cases where pods get evicted should now update the status of the step as failed instead of the builds just hanging.​ (CI-3495, ZD-27504, ZD-27966)
  • Improved error message handling in case resources aren't available and handled case with empty containers​ (CI-3487)
  • Dropdown now shows Delegates Setup options correctly styled​. (CI-3445)
  • Fixed bug for integer YAML fields with input set that contains allowed value.​ (CI-3398)
  • Region field is mandatory in YAML of s3 upload step.​ (CI-3203)
  • Fixed issue where pipelines with invalid image name expired instead of failing. (CI-2769​)
  • Limited length of a log line in CI builds to 70k characters. Beyond this, the first 70k characters will show up followed by ... (log line truncated)​. (CI-2495, ZD-28121)
  • Fixed issue where Deployment Logs weren't showing up. (CDS-36666, ZD-27648)
  • ​When a new tag is available for the image in the Artifactory, the Pipeline can now deploy the new tag. (CDS-36665, ZD-27648)
  • Tags API call will now be there only if dependent fields are changed.​ (CDS-36202)
  • Fixed a customer issue where a specific trigger stopped working. (CDS-36166, ZD-29386)
  • Added a fix to use service configuration from a template stage.​ (CDS-36133)
  • Wrong field was being picked up to display error message for Nexus. Fixed by adding correct field type​. (CDS-36118)
  • Fixed UI issue where Execution Inputs and Outputs didn't display properly when Details pane was floating. (CDS-36029)
  • Fixed an issue where opening a JIRA Create Step with multiple components selected resulting in a Null Pointer Exception. Added the check for multitype Jira field with correct default value. (CDS-35774)
  • Fixed a customer issue where configs were lost for a set of Pipelines. (CDS-35609, CDS-35760, ZD-29272)
  • Fixed an issue where Artifactory Connector wasn't working properly. (CDS-35716, ZD-27648)
  • Added script for deletion of passing tests screenshots after retry. (CDS-35668)
  • Fixed an issue where users were unable to dismiss template library when trying to create step template. (CDS-35624)
  • Fixed a customer issue where configs were lost for a set of Pipelines. (CDS-35609, ZD-292238, ZD-29272)
  • Fixed an issue where running a Pipeline with a Jira Create Step that has Issue Type specified as a Runtime Input results in a "Something went wrong..." message. (CDS-35312)
  • Fixed an issue where Custom Triggers would fail to run Pipelines. Now a Pipeline that contains a Step template with a user-specific scope can be triggered by a user who don't have access to the template. (CDS-35301)
  • When creating a manifest trigger, a user can now select from a list in the create wizard flow using a template. (CDS-35229)
  • Pipeline was getting saved even when the User Group was empty. (CDS-35094)
  • Fixed an issue in Terraform apply and the Terraform destroy steps where selecting the delegate and clicking on the step, the delegate selection is cleared out. (CDS-35068, ZD-28701)
  • Updated the Service and Environment DTO identifier. (CDS-35037)
  • We have fixed a bug where a disabled icon was showing on template cards when child type wasn't present. (CDS-34973)
  • The UI now shows the list of allowed values for Runtime Inputs when the value isn't in the configured set. (CDS-34966)
  • Fixed issues regarding usage of step templates in Feature Flag Stage. (CDS-34940)
  • We fixed an issue that was breaking the pipeline when a user copies a Stage template with a reference to a Step template.​ (CDS-34921)
  • We do not advise this, but you can now deploy a public deprecated Helm chart for Helm version 3.8.0. Make sure you're handling deprecated Helm charts properly.
    This fix is for Helm 3.8.0 and doesn't apply to Helm 3.1.2.
    For Helm V3.8.0, we've separated warning from output stream as part of error stream. So now unless and until there is some error in the deployment, it won't fail. It'll simply ignore the warning and carry on with the deployment. The warning will be displayed in the logs, so that you can be more careful next time. (CDS-34529, ZD-28769)
  • Fixed UI issue in Jira Create Step: When you specify an expression for a pull-down field such as Priority, the field reverts to a fixed value when you reopen the Step. (CDS-25562)
  • Fixed an issue where the "Something went wrong" page was displayed when user group was specified as a nonexistent expression while running a Pipeline. (CDS-25535)
  • Fixed an issue with batch processing jobs. (CCM-7317)

Minor Release 74410

Release Date: March 30, 2022

We're pleased to present Harness Self-Managed Enterprise Edition Minor Release 74410.

New Features and Enhancements

The following new features were added to the Harness platform components:

SRM
  • Service Reliability Management is now available on on-premise platforms. (SRM-9858)
Platform
  • Added a new Auth mechanism called Kubernetes Auth that takes serviceAccountTokenPath and role (PL-23491)
  • The default selection of Resource Group has been changed to All Resources Including Child scopes from All Resources at a particular scope. This means you can select all resources by default and only limit and create custom resource groups based on your use cases. This will not impact any existing role bindings. (PL-23255)
  • You can now create, remove, update, and delete entities for a Git Sync-enabled project using the API key. This will help you automate the onboarding on a project using harness APIs. (PL-22170)
  • The Account Overview page has a new Disable default Harness Account Manager setting. If this option is enabled, cannot use this Secret Manager for creating any new secrets. (PL-22001)
  • You can now use Hashicorp Vault Connector in NextGen using the AWS IAM authentication method. This method provides an automated mechanism to retrieve a Vault token for IAM principals and AWS EC2 instances.
    There are two authentication types present in the aws auth method: iam and ec2.
    The iam method is the recommended approach and we are supporting the same. See https://www.vaultproject.io/docs/auth/aws#iam-auth-method.
    The official Vault document describes the infrastructure required: https://www.vaultproject.io/docs/auth/aws#authentication
    This will impact users who will enable this new method of authentication for Hashicorp Vault in NextGen. (PL-21921)
  • Harness NG Pipelines now will limit the maximum number of parallel stages to 30. If you require more than 30 stages to run in parallel, please reach out to Harness Customer Success to enable the Feature Flag. Note that this does not limit the number of stages you can add to the pipeline. Limit applicable only for parallel stages. (PIE-2723)
  • We now have APIs to validate an existing pipeline without saving. Users can also validate a YAML.
  • NG now supports these new Expressions:
    • <+pipeline.triggerType> - Gives you the type of Trigger such as Manual or Webhook.
    • <+pipeline.triggeredBy.name> - Gives the name of the user, returns trigger name in case of Webhook.
    • <+pipeline.triggeredBy.email> - Gives the email of the user, returns NULL in case of Webhook. (PIE-2527)
CI
  • You can now view your test reports in an aggregated way by selecting all stages and all steps. This will help you understand the bigger picture of your test reports, especially if you are running across multiple stages. (CI-3603)
CDS
  • Customers can now add and use Docker images from Nexus and Artifactory registries in the Artifacts section of a Pipeline (NG). This is available for for Kubernetes and Native Helm deployments only.
    To use this option, make sure that your manifest files contain specific Harness expressions as described in Add Container Images as Artifacts for Kubernetes Deployments. (CDS-7728)
CCM
  • Cost Perspective URLs now include TimeRange, GroupBy, Filters, Aggregation, and Chart Type. Perspective URLs are now shareable as in Current Gen. When shared, a Cost Perspective will take users to the same state (same Filters, ChartBy, etc.) as the user who shared the URL. (CCM-5431)

Issues Fixed in the Release

  • Migration fix (SRM-9515)
  • Fixed Datadog data collection bug when some configured metrics where not visible in the result (SRM-9501)
  • Fixed New Relic data collection (SRM-9293)
  • Fixed issue: Analysis failed with error: ${displayName} could not be retried (SRM-4128, ZD-26603)
  • Fixed subscription page module cards layout (PLG-777)
  • Account Level Edition should honor the expiry license as well (PLG-761)
  • Fixed issue in Git experience: Detailed error is now shown in the popup when a user enters an incorrect repository name. (PL-23673)
  • We are now retaining previous step values in the Enable Git Experience Popup. (PL-23651)
  • Fixed issue in Git Sync: Wrong branch shown in a repo in Pipeline Run > save Input Set (PL-23626)
  • SCIM users can now be provisioned in NG even if they exist in CG. There needs to be two separate SCIM apps to be used for both CG/NG to be working together. (PL-23160, ZD-271, ZD-172, ZD-791, ZD-028, ZD-668)
  • You can now configure a logout URL in SAML Settings from the UI itself. We have added an extra field for logout URL in SAML Settings both in NG and CG. Hence you can configure and see the logout URL while configuring SAML Settings user . (PL-23106)
  • Fixed a bug where a left purple border was visible across all modals on NG-UI. (PL-23087)
  • Fixed a bug where a global styling change adversely impacted the widths of some modal dialog boxes. Reverted the previous global styling change and fixed it across specific modals in the NG UI. (PL-23065)
  • Fixed a bug where a global styling change had adverse impact on widths of some modals (PL-23050)
  • Enabling ng-auth-ui in on-prem builds is now behind a environment variable. (PL-22728)
  • Fixed a UI bug where some fields seemed to be extending out of the modal. (PL-22559)
  • Values are not retaining if a user clicks on the previous step. (PL-22418)
  • The Git Sync feature was not working for accounts that use the vanity URL. We have fixed this issue in the current release. This will help you:
    • Automatically register the Git Sync webhook URL.
    • Perform the YAML changes from Git. (PL-22260, ZD-26717)
  • Popup message shown as soon as user arrives on "branch to sync" step while enabling Git Sync. (PL-22191)
  • Response message not clear if Organization is missing in request. (PL-21765)
  • Added a tooltip over a fixed input so that if a user choses a custom tag longer than the input width, it's still fully visible and selectable. (PL-21624)
  • Terraform pipeline 400 response when retrieving artifact data with Account Connector. (PIE-3072)
  • Added placeholders for all Execution step types. (PIE-3048)
  • Services overview shows "Unknown" as status for Pipeline executions where the status was Rejected or Waiting. (PIE-2909)
  • Showing Pipeline stages based on module existence, instead of status ACTIVE check. (PIE-2851)
  • Values in drop-down dialog box are hidden. (PIE-2699)
  • Zoom to Fit in Pipeline execution does not persist. (PIE-2561)
  • Use ID instead of Id in user visible strings such as UI tool tips. (PIE-2241)
  • Multi-button CSS changed for text area component. (PIE-1661)
  • "Page Not Found" appears immediately after user clicks Edit for a Trigger in a Git Sync-enabled project. (CI-3697)
  • Disable the Trigger tab or create/edit a new Trigger when the user is not on the default branch of the repository in a Git Sync-enabled project. (CI-3475, ZD-26590)
  • Annotations do not appear in Run Pipeline form if even one child field in it is a runtime input. (CI-3393)
  • NG: Stage template saved as stage step after adding/deleting stage variable. (CDS-35000, ZD-284, ZD-642, ZD-851, ZD-728, ZD-758)
  • With this fix, if a values.yaml or a Kustomize patch references a non-existent expression, the workflow fails on the Fetch File step with an error message that the expression does not exist. (CDS-34981, ZD-26598)
  • "Stage" should be uppercase in the UI. (CDS-34953)
  • Users can now easily create and manage all the variables used in the stage templates with the variables panel in the template studio. (CDS-34045)
  • You can now see the exact error when the Connector cannot fetch the Jira projects. (CDS-25448)

Delegate Version

74410

Minor Release 73807

Release Date: February 23, 2022

We're pleased to present Harness On-Premise Minor Release 73807.

New Features and Enhancements

The following new features were added to the Harness platform components:

Platform
  • Harness provides an option to resume Pipeline executions from any executed Stage or from the failed Stage. These options enable you to quickly rerun stages after you identify the cause of the failure. You can click the failed deployment that you want to retry and click Retry Failed Pipeline. (PIE-2441)
CD
  • Kubernetes Cluster connection validation also includes validating the credentials. Previously, only the master URL was validated. (CDS-7304)
CCM
  • N/A
CV
  • N/A

Issues Fixed in the Release

  • Harness to Git commit defaults to Harness_User as the committer (PL-20317, ZD-21850, ZD-26717, ZD-27219)
    • Harness to Git commit was showing Harness_User as the committer. Now you'll be able to see the correct username as committer on GitHub. If you are using the same email Id for Harness login and GitHub, then your username will be shown as committer. If not, the Username provided on the Harness Source Code Manager is shown.
  • The cluster name didn't appear in the UI for Kubernetes Workflow Recommendations. (CCM-5179)

Component Versions

The following table lists the component versions in this release.

Name 

Version

NG Manager 

73807

CI Manager

73807

Pipeline Service

73807

Platform Service

73807

Access Control Service

73807

Change Data Capture

73807

Test Intelligence Service

release-46

NG UI

0.286.6

Minor Release 73610

Release Date: Feb 1, 2022

We're pleased to present Harness On-Premise Minor Release 73610.

New Features and Enhancements

The following new features were added to the Harness platform components:

Platform
  • N/A
CD
  • You can now delete Services from the Services dashboard (CDC-16505).
    • A Service cannot be deleted if it is being referenced in a Pipeline. To delete a Service, please remove the Service from any Pipelines.
    • You can also see what entities reference a Service using its Referenced by page:
  • Native Helm is now supported in Harness CD. This is behind feature flag NG_NATIVE_HELM. (CDP-19581)
    • Harness includes both Kubernetes and Native Helm deployments, and you can use Helm charts in both. Here's the difference:
    • Kubernetes with Helm: Harness Kubernetes deployments allow you to use your own Helm values.yaml or Helm chart (remote or local), and Harness executes the Kubernetes kubectl calls to build everything without Helm and Tiller needing to be installed in the target cluster. You can perform all deployment strategies (Rolling, Canary, Blue Green).
      See Kubernetes CD QuickstartHelm Chart CD Quickstart.
    • Native Helm: For Harness Native Helm deployments, you must always have Helm and Tiller running on one pod in your target cluster and Tiller makes the API calls to Kubernetes. You can perform a Rolling deployment strategy only.
    • See Native Helm Quickstart.
CCM
CV
  • N/A

Issues Fixed in the Release

  • Harness On-Prem CIE not seeing status checks with account level repository connector (CI-3187, ZD-20607)
  • Pipeline keeps running even after approver rejects the approval (CDC-16549, ZD-26346)
    • When an Approval step is rejected, the Failure Strategy Unknown errors is considered. Now, Ignore Failure, Mark as success, and Abort Failure are used.

Component Versions

The following table lists the component versions in this release.

Name 

Version

NG Manager 

73610

CI Manager

73610

Pipeline Service

73610

Platform Service

73610

Access Control Service

73610

Change Data Capture

73610

Test Intelligence Service

release-46

NG UI

0.284.7

Minor Release 73406

Release Date: Jan 18, 2022

We're pleased to present Harness On-Premise Minor Release 73406.

New Features and Enhancements

The following new features were added to the Harness platform components:

Platform
  • Harness Git Experience Git Sync Error Reporting (PL-21838)
CD
  • N/A
CCM
  • GCP Cloud Cost Connector setup now requires explicit table name to be entered (CCM-5245)
    • Cloud Billing export to BigQuery enables you to export detailed Google Cloud billing data (such as usage and cost estimate data) automatically throughout the day to a BigQuery dataset that you specify.
    • By requiring an explicit table name the data sync logic with Harness is now simpler.
    • Action: Existing GCP Cloud Cost Connectors will continue working as normal.
    • See GCP Billing Export.
CV
  • N/A

Issues Fixed in the Release

  • No issues in this release.

Component Versions

The following table lists the component versions in this release.

Name 

Version

NG Manager 

73406

CI Manager

73406

Pipeline Service

73406

Platform Service

73406

Access Control Service

73406

Change Data Capture

73406

Test Intelligence Service

release-46

NG UI

0.282.3

Minor Release 73225

Release Date: Jan 6, 2022

We're pleased to present Harness On-Premise Minor Release 73225.

New Features and Enhancements

The following new features were added to the Harness platform components:

  • You can now perform the following on Perspectives (CCM-5260)
    • Filter Perspectives based on Cloud Providers
    • Filter default OOTB Perspectives
    • Access Recently Edited Perspectives
    • See Create Cost Perspectives
  • In Harness CCM Budgets you can now (CCM-5232)
    • Define budget over multiple periods
    • Define the start period for a budget
    • Add multiple budgets for a single Perspective
    • View confirmation pop-up when a budget is deleted
    • See Create a Budget

Issues Fixed in the Release

  • Build Bitbucket with tag was not working. (CI-3139, ZD-20670,ZD-21315)
  • Retry action on Initialize step to build CIE K8s pod was not working with Stage Failure Strategy.(CI-2954, ZD-20678)
  • Unknown Error message about proxy/http task failing (CDC-16289, ZD-20959)
    • HTTP step failed with an error: Invalid Request: Delegate is configured not to use proxy for the given URL. Happened when proxy was set on Delegate and the URL provided in HTTP step was added as no_proxy. We have fixed it with this release.

Component Versions

The following table lists the component versions in this release.

Name 

Version

NG Manager 

73225

CI Manager

73225

Pipeline Service

73225

Platform Service

73225

Access Control Service

73225

Change Data Capture

73225

Test Intelligence Service

release-46

NG UI

0.280.10


Please Provide Feedback