Feature Requests

Create an EKS add-on that deploys the Harness GitOps agent. This will allow to seamlessly deploy GitOps agents to cluster without requiring extra steps from the end-user.

Create an EKS add-on that deploys the Harness Delegate related component. It would simplify private cluster setup and limit manual steps to set up connectivity between Harness and EKS.

Upgrade MacOS image Xcode 16.3 for CI builds

Currently the expression suggestion does not show up in the email body. However, the expression resolution works fine and the YAML view still provides the suggestion when the body content is edited. Providing the suggestions for email body shall provide better user experience.

Support artifact download as part of the "Copy" command in WinRM deployments Currently, the WinRM deployment type only supports artifact download through the "Download Artifact" step. The "Copy" command does not support artifact transfer—only config files are copied using this method. We request support for downloading and copying artifacts as part of the "Copy" command in WinRM deployments to streamline the deployment process.

Hello Team, I am encountering an issue with the test reports feature in the CI pipeline. After the pipeline runs, the test reports are displayed in the console. However, I have noticed that only the failed tests have complete execution logs. For better debugging and analysis, I would like to have the execution logs for the passed tests displayed as well. Expected Behavior: The execution logs for both passed and failed tests should be displayed in the console. Actual Behavior: Only the failed tests have complete execution logs, while the passed tests do not. Environment: Harness CI Pipeline URL: https://transunion.harness.io/ng/account/HgTKqISVTX-kQSVsWCHEcA/all/orgs/OneTru/projects/OneTru_Platform/pipelines/ipass_ui_automation_java_17/executions/Uqs8PbMERkezEnP_T3gADw/tests?connectorRef=&repoName=Harness_pipelines&branch=feature%2Fipass-tag&storeType=REMOTE&step=TB6421VpSuWnHpQP0IE1Ww&stage=OhXfH2gJRVySO3as_YR3nw&childStage=&stageExecId= Thank you for your assistance. Best regards, Uday Gagguturu

Currently either from Execution History or over of a specific service, we can only look through deployments for specific Environments. We would like to see the infrastructures in there. We have multiple infras in each environment and it would be really helpful to see this information without having to dig through each execution.

We have new requirement from one of customer is to maintain local copy of the code repo with a continuous sync using a mirror option similar to what we have in gitlab and bitbucket. Once configured every commit will have sync done on the target code repo.

Need an account level configuration to set the Execution History default to something > 30 days. I know we could set a filter to display more than 30 days, but it's a pain as it needs to be setup for every project and is not a default, so it needs to be selected. An acceptable option would be to display < 30 days if there are any recent executions to show, otherwise use the configured default and display executions < the set default. Let me know if this needs more explanation. Thanks, Brian Stevenson

The Harness API is very difficult to use because of all the inconsistencies. To name a few: no standards in how api calls are done. no consistent CRUD calls for the resources. URLs are all over the place. paging is done at least three different ways documentation is very sparse and missing key details, example: what is the syntax of the sortOrder query parameter? documentation shows many "beta" apis, with no indication of whether they should or could be used. I’ve encountered three different ways to do paging for APIs that return lots of entities: Use query params size and page, return in response headers to return paging information, example: https://apidocs.harness.io/tag/Project-Roles#operation/list-roles-project Use query params size and page, return in body , totalElements, totalPages, size, number example https://apidocs.harness.io/tag/Pipeline-Execution-Details/#operation/getListOfExecutions Use query params pageSize and pageIndex, return in body , totalPages, totalItems, pageItemCount, pageSize example: https://apidocs.harness.io/tag/Project-Roles#operation/list-roles-project The REST API standards could come in very handy and make the API more useable.