Feature Requests

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

In FG, We have services that use a custom artifact source that points to a template. When creating a trigger, they can refer to those custom artifact sources against the service and use them as needed. In NG, feature parity is missing. A trigger does not offer an option to select the artifact source from the service; We only see utilizing a custom option. However, there does not appear to be any way to choose a custom artifact source template. We would have to place a custom script for each trigger. This goes against standardization principals we have as an organization

Based on the documentation I don't see a way to get this, but all of our application logs are being ingested by Dynatrace and I would like to be able to import those logs into Harness so they can be evaluated by continuous verification

We're trying to use the AWS Pod Identity association feature in AWS EKS, but it doesn't seem to be working. Could you please enable support for this feature?

To obtain GitX webhook events via the Harness API, a feature is needed to expose webhook event data (e.g., commits, PRs, issues) from Git repositories integrated with GitX. This would allow users to programmatically retrieve and act upon events through API endpoints. Raising this feature request ensures seamless event handling across workflows.

Currently, git connector is expecting a tockenref in the PAT section and we can't use any Harness expression in this field due to this we can't use pre-existing secret from azure vault without creating a secret reference. Need have the git connector accept the Harness expression so that we can use pre-existing secret from azure vault without creating a secret reference in Harness.

The Overview page for a project doesn't have a section for description. Please add one where we can link to documentation.

If delegate pods were scaled down then as part of delegate notification its not working although configured as below: https://developer.harness.io/docs/platform/notifications/manage-notifications/ Also we can see as part of notification rule we can not use delegate tag and need to pass/select the delegate name, as with tag notification is not working

Does Harness CI module has first class integration with AWS Codebuild? The expectation is to: Call AWS codebuild job While code build job running, it should tail the logs of AWS codebuild on harness UI On stop of step on harness UI, it should stop AWS code build job. On stop of AWS code build job through AWS console, harness UI should show it stopped.

Currently the Freeze Window is applicable to the CD stage. Due to this any pipelines that are run during the Freeze Window will be aborted. There are use cases where users would want to run Dryrun to production and this is not possible when the freeze is enabled. This request is to provide a provision to run dryrun for prod during the freeze window where there is really not any changes being rolled out.