Feature Requests

For container Run step, use the image entrypoint defined in the dockerfile instead of requiring shell and command fields. This works only for background step at the moment. It would be useful for Run steps as well. The use case is to run some tests where the image is already set up to run them. It should be blocking (not background) since it is for running smoke tests.

Hi, As we are moving from bitbucket pipeline to harness, in bitbucket we have an option to remove the older cache from the pipeline. In Harness pipeline also we want to remove older cache. We have enabled our cache intelligence in harness pipeline build stage. Now we want to remove older cache from harness pipeline. Please guide us on this

In Harness pipeline we want to remove older cache. We have enabled our cache intelligence in harness pipeline build stage. Now we want to remove older cache while the pipeline deployments. In Bitbucket when we are deploying, they give one option to remove the older cache from bitbucket pipeline. We want to do the same in harness pipeline.

We are planning to create a deployment solution for Web Logic and wanted to check what offerings Harness provide for the same. Please let me know when I can schedule a call with you.

We would like to request an enhancement to the GitOps capabilities in Harness to natively support progressive delivery workflow, combined with in-pipeline verification, and controlled rollout management. The goal is to allow GitOps-enabled services to be deployed and managed entirely from within a Harness pipeline, including percentage-based rollouts, verification gates, approval gates and drift protection mechanism.

Due to a large number of clients with varying deployment configurations, we have pipelines that have close to 100 input sets. When the pipeline changes we are required to reconcile each input set individually. This is VERY cumbersome. Please provide a button (or an option on the ellipsis) on the pipeline that will reconcile and save all input sets. As per ticket #87746, the support representative verified that this feature does not exist.

Currently, in the containerised step group, the images pinned for CI are not respected, and for tasks like git clone, it uses a random image version of git clone. Here, we want the containerised step group in the CD/Custom stage should also obey the image pinned for CI and use the same images. https://developer.harness.io/docs/continuous-integration/use-ci/set-up-build-infrastructure/harness-ci/#specify-the-harness-ci-images-used-in-your-pipelines Example use case - Google Cloud Run deployment.

Currently the Harness MCP server runs on stdio locally with API tokens, this is not very enterprise friendly. We need the server to run remotely using http-streamable and use OAUTH authentication.

Currently, the Gihub Connector when using the App Token (PEM) requires a file to be uploaded to Harness in order to be utilized with the connector. While this is possible this it not an ideal automated function ( https://developer.harness.io/docs/platform/connectors/code-repositories/git-hub-app-support/#configure-the-github-connector ) We would like more options to be able to add this token because we want it to be able to be rotated without a manual process involved. We'd like either to be able to take a reference file from Vault and utilize it within this field, so we can update vault with the new file and it will be served everywhere.... OR the ability to save the PEM token file content as a secret within Harness and then reference that secret within the Github Connector, when setting up a Github App connection.

Harness has a native step for uploading artifacts/files to s3, but we could use something similar for GCS