Feature Requests

Wanted to create the dashboard for policy and Governance therefore need the ability for this

Right now, we can either mark the whole result as applied or ignored, but we can't for individual line items inside the recommendation. Either split each line item into an individual Recommendation, or allow us to mark an individual result inside the Recommendation as Applied or Ignore.

Hello, we would like to be able to handle triggers in git experience same as pipelines and input sets. Currently everything but triggers is able to be maintained by git experience, leading to a situation where you think everything is managed in code, but it really is not and you are missing context as to how things work. This is especially true when onboarding new engineers onto Harness and causes unnecessary confusion. Thanks

Create a centralized UI dashboard within Harness to view and manage enabled Feature Flags across the platform. Currently, users must call APIs to discover which feature flags are active. A UI would provide visibility, searchability, and ease of management for feature flag configurations, improving operational efficiency and troubleshooting capabilities.

Helm Services currently support multiple manifests but, K8s services do not. We'd like the ability to add multiple manifests to our Services so we can select them at run time or use an expression to dynamically switch them.

When using the DBApply step, if there is an error users are required to set up a second run step to parse execution logs for error messages to update ticketing systems, having the errors as an accesible expression during rollback would be really useful.

We have an audit need to attach items to our servicenow ticketing system. This is supported by the API but not harness native steps. while a scripted workaround is possible, it creates a burden on our developers.

We have setup the GitOps Agent long ago and multiple projects are using the same for their GitOps applications. Recently, we learned that Harness GitOps agent support DR natively and we want to use the same. However, it requires to create a new GitOps agent that has an impact to the existing applications. We are looking for out of the box support from the Harness and provide seamless experience to our users. Ask is to migrate the GitOps application from existing Agent to the new Agent (DR enabled with all new features).

Steps defined within Stage Templates are not available for selection in the Step Failure Notification configuration under Pipeline Notifications, as Harness currently does not support template resolution for pipelines using Stage Templates.

Hi Team, Unable to adjust the schedules priority order inside as rule using terraform. we can only adjust using manually. We need support to set the order priority of scheduled inside a rule as well. Sample terraform code rule with 4 schedules. these 4 schedules are added randomly. Please refer attached tf file for used terraform code for rule with 4 schedules without priority. resource "harness_autostopping_rule_vm" "aws_vm" { name = "cpms-aws-ec2-01-us-work-hours1" cloud_connector_id = var.cloud _connector_id idle_time_mins = 5 filter { vm_ids = [ "i-xxx" ] regions = [ "us-east-2" ] } dry_run = false } Priorities test resource "harness_autostopping_schedule" "MondayThroughFridayUptimeFrom9amTo6pm_vm" { name = "MondayThroughFridayUptimeFrom9amTo6pm_vm" schedule_type = "uptime" time_zone = "EST" starting_from = "2025-01-02 15:04:05" repeats { days = ["MON", "TUE", "WED", "THU", "FRI"] start_time = "21:46" end_time = "22:00" } rules = concat([ harness_autostopping_rule_ vm.aws _ vm.id harness_autostopping_rule_ rds.aws _ rds.id , harness_autostopping_rule_scale_ group.aws _ asg.id ]) } resource "harness_autostopping_schedule" "twopmto3pmDowntimeOnWeekDays" { name = "twopmto3pmDowntimeOnWeekDays_2" schedule_type = "downtime" time_zone = "EST" starting_from = "2025-01-02 15:04:05" repeats { days = ["MON", "TUE", "WED", "THU", "FRI"] start_time = "14:01" end_time = "15:00" } rules = concat([ harness_autostopping_rule_ vm.aws _ vm.id harness_autostopping_rule_ rds.aws _ rds.id , harness_autostopping_rule_scale_ group.aws _ asg.id ]) } resource "harness_autostopping_schedule" "OverNightDowntimeOnWeekDays" { name = "OverNightDowntimeOnWeekDays_3" schedule_type = "downtime" time_zone = "EST" starting_from = "2026-01-02 15:04:05" repeats { days = ["MON", "TUE", "WED", "THU", "FRI"] start_time = "17:02" end_time = "18:00" } rules = concat([ harness_autostopping_rule_ vm.aws _ vm.id harness_autostopping_rule_ rds.aws _ rds.id , harness_autostopping_rule_scale_ group.aws _ asg.id ]) } resource "harness_autostopping_schedule" "CompleteDownTimeOnWeekEnd" { name = "CompleteDownTimeOnWeekEnd_4" schedule_type = "downtime" time_zone = "EST" starting_from = "2025-01-03 15:04:05" repeats { days = ["SUN", "SAT"] } rules = concat([ harness_autostopping_rule_ vm.aws _ vm.id harness_autostopping_rule_ rds.aws _ rds.id , harness_autostopping_rule_scale_ group.aws _ asg.id ]) }