Feature Requests

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.

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?

Please make the emails of your recipients box in the notification section of a pipeline able to perform expression resolution. Pipeline -> notify -> new notification -> on failure -> email -> <+expression of user email based on who approved something in the pipeline> <+ pipeline.stages.Run _terraform.spec.execution.steps.HarnessApproval_1.output.approvalActivities[0]. user.email > This could be as easy as removing or changing a regex validation for the box.

Account level Environment Groups should be able to add Org and Project level environments to it's list.

FR - Currently, I see that we provide an option to choose branch during the initial creating of service but there is no option to change branch post that. we would like to have a feature to change default branch of service or to choose branch of service in pipeline for remote service.

Summary: Enhance the pipeline management functionality in Harness to allow users to easily identify and backtrack through services linked to multiple pipelines. This request addresses the frustration experienced when users cannot reference services within pipelines due to the current fixed value inclusion method. Details: Currently, when a service is included in a pipeline via calling a template where the service is taken as a fixed value, it becomes challenging for users to backtrack and identify all the pipelines that reference the given service. This limitation impacts the ability to efficiently manage and troubleshoot pipelines and services across the organization. Proposed Enhancements: Service-to-Pipeline Mapping: Implement a feature that maps and displays all pipelines referencing a specific service, regardless of how the service is included (e.g., via template with fixed value). Provide a dedicated interface or view where users can see this mapping clearly. Service Reference Tracking: Allow services to be referenced in pipelines dynamically, and ensure these references are traceable and visible to users. Enable a mechanism for users to easily navigate from a service to all its associated pipelines within the Harness interface. Enhanced Template Management: Update the template management system to support dynamic referencing and tracking of services included within templates. Ensure templates provide visibility into which services they include and which pipelines utilize these templates. Audit and Reporting: Introduce audit logs and reporting capabilities that detail the associations between services and pipelines. Provide automated reports or dashboards that highlight service-to-pipeline linkages, making it easier for users to track and manage dependencies. Benefits: Improved Visibility: Users can quickly identify and understand the relationship between services and pipelines. Enhanced Troubleshooting: Easier backtracking through services to pipelines aids in faster issue resolution. Efficient Management: Simplifies the process of managing multiple pipelines and their dependencies on services. Scalability: Supports the scaling of pipeline infrastructure by providing robust tracking and referencing capabilities. Reference to internal ticket: https://support.harness.io/hc/en-us/requests/67281

If using a Pipeline Template to create a Pipeline, we are unable to add additional Pipeline Variables to the Pipeline. We can add Pipeline Variables to the Pipeline Template directly and those work however, if we wanted to add additional Variables to the generated Pipeline, the Add Variables Button is greyed out. Adding variables via the Pipeline YAML results in unexpected behavior and doesn't show up properly.

Currently in the Manual Approval step only fixed values or expressions are allowed in the Approver Input. We need an input with list of values to select from. Like in the allowed values of runtime input fields that is currently available at the pipeline and stage level variables.

We need to support import from git option for OPA Policies