Feature Requests

Require a REST API that could get us the SBOM score for the specified artifact.

At present a Stage Template with its Looping Strategy exposed as <+input> works fine provided a value is provided, but fails if no looping strategy is provided. We would like a way to set a default strategy, e.g. repeat times 1, so that we can expose flexible looping capability but also maintain simple operation for template consumers with no looping requirement

The Centralized Notifications for Pipeline feature ( https://developer.harness.io/docs/platform/notifications/centralised-notification/ ) currently supports DataDog as a notification method but does not include Dynatrace. This request is to add Dynatrace as a first-class integration, making it available as a selectable notification method in the dropdown menu.

Entities (such as pipelines/services etc) that are maintained in a remote repo (such as github) does not contain the Verified tag on the commit when pushed from Harness. This request is to have the feature for signing commits when pushing commits to github so that they show up as verified.

Hi Team, we want to enable the notification in MS Teams for all the pipelines for different events under a harness project. We see the option of notifications management under project settings in UI. We understand that the terraform resource "harness_platform_notification_rule" is also available, though as checked with support team, It is currently only available for the SRM and SLO module. Could you please made this terraform resource available for the pipelines as well. https://registry.terraform.io/providers/harness/harness/latest/docs/resources/platform_notification_rule

We are building various nuget packages using the Microsoft .Net 6.0,7.0 and 8.0. The package is pushed via JFrog connector that doesn't contain the nuget build info. This is a critical requirement for the Jfrog Xray SCA scan. Here are the build info details that provided by the JFrog. We need to pass along the build info while running and uploading to Artifactory. Build info is JFrog source to identify dependencies. Xray will request for the build-info, which contains the list of artifacts and dependencies to scan. Using this information, whatever the build info is able to pick up during the build process, Xray can attempt to match "transitive dependencies" and include it in the analysis. You can find more information on it below: https://www.buildinfo.org/ And an npm/donet example of build passing the build info: https://github.com/jfrog/project-examples/tree/master/npm-example https://github.com/jfrog/project-examples/tree/master/msbuild-example

Hi team, currently feature flag git sync only supports syncing of all feature flags in 1 project into 1 yaml file. the issue with this approach is with maintainability. instead of having 1 giant yaml file, allow us to split this across multiple smaller yaml files that can be easily maintained by multiple teams.

When actioning a recommendation Engineers often find the recommendation too harsh or contravenes a SaaS requirement, but they are able to implement a partial action of the recommendation and estimate their own more appropriate amount for the Savings $$$ figure. The integrations with Jira and SNow need to allow for the setting of the new amount when closing the ticket, populating the recommendation in Harness with the new estimated savings amount. They do not do this currently

Allow a recommendation to remain as listed once it has been put into a new "In Progress Status". This gives the engineer a chance to return to the tool to register the action taken and provide a fair estimation of the actual savings gained. Sometimes it takes a few weeks before the savings can be seen in enough data to prove the value of the actioned recommendation. A5t the moment the Engineer only has until the next update, when the recommendation may just disappear! Mad!

Currently unable to roll back the changes made at policy from UI. Require a native feature to roll back to the previous change via the UI.