Feature Requests

Currently, output variables of type Secret are only supported for the Run and Shell Script steps. We'd like this functionality extended to Plugin steps as well. Use Case: We have a plugin that generates a short-lived GitHub token and returns it as an output variable, which subsequent steps in the pipeline use. We're looking for a way to instruct Harness to treat this output as a Secret, ensuring it is masked in logs, UI, and other exposed locations for security purposes.

Now developers need to re-run a previously executed pipeline in order to mimic a rollback to a stable version. We would like to have a simple button that rollbacks to a previously deployed successfuly version

I would like to request the ability to publish test reports from a Run step within a Custom Stage or Step Group. These types of stages are used to execute QE automation scripts and will provide a lot of benefits for viewing results and providing summary of state of automation test runs.

There is a new parameter available on the GitOps API called fetchFromHarness It would be nice to have the option to fetch using this on GitOps CD Steps

Hello. While Dynamically provisioning infrastructure with Terraform has been useful https://developer.harness.io/docs/continuous-delivery/cd-infrastructure/terraform-infra/provision-infra-dynamically-with-terraform/ , It has been less useful in its application, since we cannot define things like ServiceDefinition dynamically. Only Task definition can be done so, and as such, this makes it difficult for us to fully utilize a Dynamically Provisioned Infrastructure. We'd like the ability to do so in order to support a 1-step process for our deployments

We need a way to trigger harness pipeline using git tags via git experience. Currently we have the feature to run them from branches only. The feature is needed to be available on the UI as well as some API support as well.

All pipelines are messed up, i can see CI pipeline in CD and CD pipeline in CI. Need this enhancement to segregate based on CI and CD pipeline.

Scenario: You want shell script step output a variable even when script execution fails. An example below. I am checking if DNS name exists. If it doesn't exist I want to fail the step so I can do failure execution strategy of retry mark as success. At same time I want output variable available so I can use the output variable in subsequent steps. However afaik there is no way to do an output variable if you want to mark step as failure. set +e echo "DNS name to test: $dnsname" host $dnsname dnsteststatus=$? echo "DNS test returned status: $dnsteststatus" if [ "$dnsteststatus" -eq 0 ]; then echo "DNS name for $dnsname was found in DNS" else echo "DNS name for $dnsname was not found in DNS" fi Ex script.

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

We need cache restore steps to fasten the CDK builds