Feature Requests

Would like to achieve queue step in build stage now through CI pipelines Example: pipelineA: execution 1====>running-----stepA passed execution 2====>running-----stepA not hit yet execution 3====>running-----stepA running execution 4====>running up to stepA, then wait until all 3 running execution (1-3) completed step A, then I can start stepA As per ENG: we can have a step which always executes that does the cleanup or have a ttl associated with the key.

Currently the only way to jump to an individual pipeline view form a pipeline chain is to scroll to the very right of the unfolded individual pipeline (which can take a long time!) and find a link in the top right of its rectangle. It's very slow. For some reason there is no link in the console view at all. I'd like to have a faster way to jump to a child pipeline view. Would be great to have links in the console view.

With larger enterprises willing to use Harness's IP allowlisting feature, its important to have a bulk IP upload API since today both UI and API only have options for individual IPs.

Is there anyway to prevent terraform outputs marked as "sensitive" from being displayed in the Output tab (and other places) CDS_ENCRYPT_TERRAFORM_APPLY_JSON_OUTPUT encrypts the entire terraform output into a single Harness Output field. How do I then get individual values from the encrypted field?

Support to deploy in ACA (Azure Container Apps)

Currently the TAS services can be deployed using CF CLI 7.0. This feature request is to enable the support for TAS deployments using CF cli 8.0

I believe it’s a good idea to integrate Dependabot with the Harness codebase. You can use open-source projects such as Mend Renovate and build capabilities like internal organization dependency checks from your own artifact modules, JFrog, etc. This integration will enable DevEx teams to publish new inter-organization packages while ensuring that teams keep their dependencies up to date. It will also help development teams track their dependency versioning effectively.

Currently helm lint feature is not available out of the box and users have to rely on the hooks on the service to lint the helm chart that requires custom scripting. This request is to have helm lint support for helm services (Both native helm and K8s) in harness.

Currently the steps for helm deployments are limited to deploy/rollback/delete etc and the helm commands are included part of these steps. However, Having a separate step that has configurable helm commands would give more control and help leverage the helm features.

Currently, Harness doesn’t support in-house or on-premises Azure DevOps TFS setups for Git with API access. can you add this feature?