Feature Requests

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.

Changes made directly in Github do not go through any validation. Harness only validates pipeline changes done through Harness UI. If we are to make a change to 300+ pipelines via Github, there is no way to run this validation right now. Request is to expose Harness validation API or build a feature where users can easily validate their feature branches.

When viewing exemptions at the account level, it would be helpful to have filters to view exemptions tool-wise. Additionally, having the option to filter by the requester would be an added advantage, as it would allow us to quickly fetch details for a specific tool raised by a particular person.

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

There is no native feature that provides recommendations based on Azure Reserved Instances (RI) or Azure Savings Plans. Request: Enhance the CCM (Cloud Cost Management) module to: Provide savings recommendations based on Azure Reserved Instances. Provide savings recommendations based on Azure Savings Plans.

For build executions, we would like to be able to view actual pod usage metrics (CPU, memory, and disk) within the Harness UI. Currently, the only way to view these metrics is by viewing logs within our clusters.

When you press the "Re-run Pipeline" button on the UI, there is no connection between the previous Execution and the new one. There is no way to check which pipeline you are rerunning, only the inputs are copied. It would be nice to reference that can be checked using JEXL at runtime, maybe something like <+pipeline.previousExecution> similar to how we have <+pipeline.originalExecution> during rollbacks. I know this is more engineering work because they are different executions.

In the v2.73.0 Azure CLI, they deprecated the use of --username which breaks Harness Azure Deployments. We'd like for Harness to upgrade their deployment code to work with this CLI version later versions as well.

In the GitOps release step, the order of fields in the YAML file changes, which affects readability for our end users. It would be beneficial if the fields could remain in their original order to maintain clarity and consistency.

There is a new parameter available on the GitOps API called fetchFromHarness It would be nice to have the option to fetch using this on GitOps CD Steps