Feature Requests

We have set up user groups to receive notifications in the Microsoft Teams channel when approvals are required. However, it is currently not possible to approve requests directly within the Teams channel. Raising this feature request to enable approval actions via the Teams channel.

Basically, In CI Pipelines we observe that the test results will be published to the Tests tab. Likewise, we need to have the same for CD Pipeline also. But in one of the CD pipeline I'm unable to publish the test results to the Tests tab even after using right plugin. Enable the right feature request to publish the test results (Ex: JUnit XML from .NET Smoke Tests) in Tests tab of CD pipelines.

The GitOps Helm Chart currently only supports adding the agentSecret directly in the values.yaml file. We'd like the ability to define an existing K8S secret here instead of putting the secret in the values.yaml file as plain text. Our organization uses External Secrets Operator (ESO) to fetch secrets from AWS Secrets Manager and create Kubernetes secrets automatically. We need the ability to reference these existing secrets in the Helm chart rather than embedding secret values directly in values.yaml.

We'd like to remove the unused values in the values.yaml file in the BYOA GitOps Helm Chart. https://github.com/harness/gitops-helm-byoa/blob/8792d63df3845103f0db980e9df53b8f479633e0/charts/values.yaml#L399 For example, the values in global.image are not used anywhere here and just cause confusion for users.

Currently In the pipeline details page, the UI displays the Pipeline name directly from the YAML. However, when switching to Input Sets, the name is fetched from the metadata value stored in the database at the time of pipeline creation. Because of this, if the name is later updated in the YAML, the Input Sets view will still display the original metadata value.

We need some way to tell when a pipeline was invoked directly or when it was invoked as a sub pipeline of another pipeline. This would allow us to condition some stages in the pipeline based on the source of the execution

We cannot tell if someone aborted the verification step when Abort Verification is used. https://developer.harness.io/docs/continuous-delivery/verify/configure-cv/abort-verification/ We cannot tell historically when looking at the pipeline. It only appears as a success or failure with a general "error"

We'd like to add secret/expression support when creating GitOps clusters. Currently, any of the authentication methods require the user to input passwords, tokens, certs, etc as plaintext. We'd like the ability to pull these from secrets instead.

When I update a pipeline stored in Git, the platform automatically sets up everything, including the PR, and then closes the modal. However, I would greatly appreciate the ability to view the newly created PRs immediately, rather than having to navigate to GitHub and conduct a search.

We'd like the ability to add an Approval step after the Prepare task runs in a Helm Deployment step.