Feature Requests

Many reports such as coverage, linters, unit tests from various languages, etc use proprietary HTML reports. Harness enables you to upload these reports as artifacts to S3 or similar, but it does not support HTML reports natively. I would like to see this feature make it to Harness similar to https://plugins.jenkins.io/htmlpublisher/ to support additional quality and build reports

VM Pools for Windows require a lot more time for their image creation and "healthy" State to be established. There needs to be a method to be able to adjust the init timing on the VM creation.

Similar to the CD module user would like to have the Approval as a CI step.

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

I want to use the AWS connector permission in S3 cache/restore step to access S3 however S3 cache/restore step is currently using the permission on the stage infrastructure connector. Expected behavior: When we specify an AWS connector in the S3 cache/restore step, we need to use the permission of AWS connector to access S3 rather than using the permissions defined in the stage infrastructure connector Observed behavior: In order to access S3 currently we don't use the permission of AWS connector configured in the S3 cache/restore step instead we use the permissions of stage infrastructure connector

Needing be able to build and upload Universal Package (.zip based) artifacts to Azure Artifacts that are being used for Azure Functions.

We are planning to roll out an OIDC-based authentication approach for the Harness delegate. As part of this, we have created a trusted relationship in the target AWS APPCI account and set up the HNS namespace within one of the apps. Additionally, we created a service account in the delegated cluster by providing the AppCI role ARN. However, we are encountering a blocker. While we are able to see the configuration for the CI stage, we are unable to see the options for CD. We would appreciate your assistance in troubleshooting this issue. Specifically, we would like your help to test a sample pipeline using the OIDC-based approach for both CI and CD in the delegate setup. This will help us successfully complete our POC. Looking forward to your guidance on resolving this issue.

It would be useful if we could set a node selector or tolerations for Harness pods. I know this can be done at the pipeline level, but I would like to be able to do this globally, perhaps at the Kubernetes connector level. So we would be able to set a default node selector and toleration, but if one has been set at the pipeline level this would override the default. This would apply to delegates and to pods created by pipelines.

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

While executing the pipeline, how to hide the code/script being displayed in the execution logs.