Feature Requests

Pipeline Stages do not have a default branch setting like other GitEx entities. This causes issues with IDP if the branch is not explicitly defined and the branch is coming back as null.

Hello Team, As a part of our process, we run quite a few preparation steps utilizing applications like Ansible. When an error occurs for our dev team we spit out logs and create a bundled zip for these logs. We would like for these logs to be held somewhere in Harness so that they can be easily available for our teams to troubleshoot in the event of a failure. What we would like is for harness to have a built in tab that could be populated with useful artifacts from the pipeline (such as these logs) so that troubleshooting can take place quickly. Customers should be able to upload and store what they need in this tab as an output from the pipeline, and that way our teams can troubleshoot issues with a one click download. It would also be nice if Harness entity items such as Delegate logs and pipeline execution/step logs could be included.

In the GitOps release step, the order of fields in the YAML file changes, which affects readability for our end users. It would be beneficial if the fields could remain in their original order to maintain clarity and consistency.

When using the containerised step group in Cloud Run deploy type, we need to run the container non-privileged, but the download manifests step prevents this as it doesn't honour the step group config. There's also no config option on the step itself to run as a non-root user or non-privileged user. The Download manifest option should have option to run as non-privileged or non root mode.

In the v2.73.0 Azure CLI, they deprecated the use of --username which breaks Harness Azure Deployments. We'd like for Harness to upgrade their deployment code to work with this CLI version later versions as well.

In the list execution API, by default we show last one months data, if any one need to see a older data, he needs to add a timeframe here, but there is no mention about the timeframe field in the API doc page - https://apidocs.harness.io/tag/Pipeline-Execution-Details/#operation/getListOfExecutions Please update this API doc page to add details about this frame and also any other options which we allow from the UI and not mentioned here.

I'm using the AWS CDK steps and would like to have more frequent updates to the image used by the step.

Segregation of CI and CD pipelines for easy maintenance and better readability. Folder structure for maintaining CI and CD pipelines based on services or tech stack.

IRSA-based authentication for Azure or GCP for adding GitOps Cluster. IRSA-based authentication is currently supported only for AWS. It is not yet supported for Azure or GCP for adding GitOps Cluster Can we support the same.

Support Built In Akamai Connector In Harness To add Akamai net storage connectivity with Harness? and deploy in that using Harness Can you kindly support the Built-In Akamai Connector In Harness