Feature Requests

Widget to track status of epics and analyze work done, pending, distribution and estimation.

After Harness introduced changes regarding Overrides, we have lost the ability to have runtime branch inputs on a manifest file for our referenced environments. When attempting to edit the override, the option to switch it to runtime input appears but after a save it reverts back to a normal preset input type.

In harness STO platform, we need a centralized view of exemptions raised across all the projects. Also, whenever there is an exemption raised, there should be an notification shown/sent.

We are using several templates at the org level (steps and pipelines). Projects are consuming the pipeline templates and often need to be reconciled when variables or other elements in templates change. Is there a way to programatically (API endpoint, Terraform) reconcile pipelines after templates have been updated. Right now the only way I can see doing this is through the UI and manually clicking through pipelines to see which needs to be reconciled. This is adding a lot more time to using templates. Why can't the pipelines that are calling the templates just render the template at run time? I am doing a very similar approach on GitHub actions and never need to inform my upstream workflows to update themselves because a template changed. On checkout, my actions use the template ref provided. I'm guessing because the templates do not live in an SCM system, that the Harness pipeline that is referencing the template needs to store a cached copy of the template? The whole reconcile pipelines does not make a lot of sense to me. I want the template to drive what is happening in the pipeline and not have to constantly make sure the "caller" pipeline is caching the template...or whatever is happening under the hood. I can understand locking a pipeline to a known good template, but isn't that why there are template versions? Which is a whole different topic.

Currently, only Pipelines, Steps, Stages, Feature Flags, Connectors, and Secrets can have naming conventions enforced. User wants this expanded to anything that can be named, such as Templates, Orgs, Projects, Approval Groups, Delegates, and User Groups. Currently there is no way to enforce naming conventions on these.

We would like to control environment name while saving the environment in project. Looks like currently Governance can be applied to the following Harness entities and events. Pipeline Feature Flag Connectors Template Custom https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/advanced/cd-governance/harness-governance-overview/#pipelines So we would like to check that the feature to invoke policy while saving the environment in the project is available or not. If not can you please let us know when can we expect this feature?

We want the ability to deploy applications and execute jobs on Google Cloud Run. https://cloud.google.com/run/docs/overview/what-is-cloud-run

Early new year App Store will stop accepting apps build on previous SDKs as IOS sdk 18 has been released on September 16,2024. Currently, Harness supports Xcode 15 on IOS sdk 17 as per following documentation: https://github.com/wings-software/harness-docs/blob/main/harness-cloud/macos-14-Readme.md

Requesting to enable PutSecretValue API as our internal organization is not authorized to use UpdateSecret.

The Governance policies set on repositories like protecting branches is available for each project, however there is no policy or way to enable the Goverance globally .