Feature Requests

Harness Cloud is a useful tool for us, but is limited due to its limits in secrets. https://developer.harness.io/docs/continuous-integration/use-ci/set-up-build-infrastructure/use-harness-cloud-build-infrastructure/#requirements-for-connectors-and-secrets We need support for access to Vault-hosted secrets.

We are looking for something that we can be set at global level that adds desired and default toleration, Affinity and annotation to all generated pods by harness. Pipeline level is not good option, since it is managed by application teams.

We are looking to perform something like the following: https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/binaries-management-with-jfrog-artifactory/build-integration#adding-files-as-build-dependencies Where teams can add build dependencies to a build This could potentially be a part of the build info plugin ( https://developer.harness.io/docs/continuous-integration/use-ci/build-and-upload-artifacts/build-and-push/build-and-push-to-docker-jfrog/#publish-build-metadata-to-a-docker-image-in-jfrog-docker-registry ) , but it may make sense as a process, so that it can be operated separately from a build

Hi, We are looking for a solution where we can run builds on ECS Fargate spot using Fargate delegates. Got to know that this is not yet supported by Harness. Request you to add this feature. Below is the ticket raised for more details https://support.harness.io/hc/en-us/requests/74427

Provide an option within the Docker build plugin to control whether the image should be pushed to Artifactory immediately after the build, allowing teams to scan the image for vulnerabilities or issues before pushing it to the repository.

Does Harness support AWS Spot instance for EC2 VM based build infrastructure farm? https://developer.harness.io/docs/continuous-integration/use-ci/set-up-build-infrastructure/vm-build-infrastructure/set-up-an-aws-vm-build-infrastructure

Feature request as suggest by Harness team to enable system level error retry mechanism for the below failures : - Pod eviction Failure to connect to addon client Connectivity errors between delegate and ci lite engine ref : https://support.harness.io/hc/en-us/requests/72479?page=1

Currently the pipeline execution list screen only allows for filtering on the repository that the pipeline yaml is stored. For use cases that use global templates, this filter is pretty useless as there is only one option, the repo the template is stored. Can we add the ability to filter executions based on the codebase URL? this will allow actually filtering based on service repository in the case of a common template

I have a gradle config that we will be using account wide based authed with pipeline defined environment variables. Currently I have to store the gradle config as a file type secret even if its not a secret. Is it possible to support file type variables?

I would like the ability to run commands inside the container of the SAM Build plugin after the build is completed, specifically jfrog build-info commands, (jf bce, jf bag, etc) to be able to append build environment/git information to a jf build that is destined for a release bundle. I don't think we can run these commands in the actual container that builds the code because we are using the --use-container option for sam build, but running them inside the runner image will be more accurate than running them in a separate step entirely.