Feature Requests

I need a access to delete non required pipelines or somehow disabled it. Because we have disabled from lightspeed but still we are seeing pipelines here in harness.

I am working on a feature where Git Actions will trigger Harness Pipelines via a webhook. It would be beneficial to have the ability to stream pipeline execution logs from the pipeline under deployment back to Git Actions or any third-party logs management service. This would help in monitoring and analyzing the logs more efficiently.

We would like to evaluate Release Orchestration module in our setup

We currently maintain separate pipelines for each microservice, but we aim to streamline the process by deploying all microservices through a single unified pipeline.

Allow looping strategies like matrix, repeat and parallel when invoking a child pipeline as a stage inside a parent pipeline.

Entities (such as pipelines/services etc) that are maintained in a remote repo (such as github) does not contain the Verified tag on the commit when pushed from Harness. This request is to have the feature for signing commits when pushing commits to github so that they show up as verified.

Request you to enable the PL_ENABLE_IN_APP_ALERTS in Harness DEV account

For traceability we would like to inject labels to kubernetes entities generated via helm deployments. We would like to be able to source the labels from harness variables or tags at the project, service, environment and pipeline level. E.g. buildversion : <+pipeline.variables.buildVersion>

We have a weird stage where we need to pause the Pipeline and redirect users to our internal platform UI. I'd like to be able to set a message that everyone can use. It's pretty much saying what the stage does and a link to my own UI for them to provide an attestation/approval so I can track it. support to display a message and a HTTP URL when the pipeline is in waiting in approval state for the users who are non-approvers when they view pipeline execution.

We would like to request support for write-only arguments for sensitive fields used in the harness_platform_gitops_repository resource within the Harness Terraform provider. Currently, GitOps repository authentication credentials such as GitHub PATs or SSH private keys are persisted in the Terraform/OpenTofu statefile because the provider does not support write-only attributes for these fields.