Feature Requests

We're trying to use the AWS Pod Identity association feature in AWS EKS, but it doesn't seem to be working. Could you please enable support for this feature?

Hi Team, I wanted to highlight an issue I’m seeing in our Harness pipeline. The console output logs are currently displaying in a different format than expected. If you look into the terraform CLI console outputs its different than the one I see in harness pipeline. Having the logs displayed in the correct and consistent format is important because it makes code reviews much easier and helps streamline the approval process. The current formatting makes it harder to read and trace the execution flow. Could you please look into this and help restore the expected log formatting? Please see the attached reference console output logs I am expecting in harness pipeline.

Developers many times reject the manual approval without any reason. We want to know why developers decided no for manual approval. This information is crucial for us to know why the pipeline failed. If we know the reason, then we can try to automate and make sure there is no need for manual approval.

Problem Statement: Currently, OPA policies cannot resolve expressions and variables during runtime evaluation. When a pipeline variable references a project-level variable (e.g., <+variable.cpu_limit>), the OPA policy receives the expression string itself rather than the resolved value. This prevents runtime governance of resource limits based on dynamically configured values. Use Case: We need to enforce CPU resource limits across all pipelines using OPA policies that evaluate at pipeline runtime. Teams should be able to configure their resource limits via project variables, but these limits must be capped by OPA policies (e.g., max 6 CPUs) during pipeline execution. Current Limitation: OPA policies work correctly on "save" when values are static At runtime, expressions are not resolved, causing policies to fail validation The PIPE_IS_PRE_STEP_OPA_POLICY_EVALUATION_ENABLED feature flag only works at step-level, requiring individual configuration per step. Also, there is no information at the step level inputs on Resource limits, so this is anyway not possible. This doesn't scale for global enforcement across custom pipelines Requested Enhancement: Enable OPA policies to resolve all expressions and variables (including project/org/account variables) during runtime evaluation at the pipeline level. This would allow: Global resource governance across all pipelines Dynamic configuration through variables while maintaining policy controls Runtime enforcement without requiring step-by-step policy configuration Support Ticket: https://support.harness.io/hc/en-us/requests/101501

Customer wants to include additional pipeline events, such as Expired, Aborted, Waiting, etc., along with Start, Success, and Failure in the same eventType condition within the UI

Restrict sensitive harness permissions in Create Role When app team creates Harness role, Role should always prefix with “abc” (eg: abc Project Admin) If Role is created with Manager User and Invite User – Restrict the Role permission Restrict Usergroup role binding only with abc Role When app team creates Harnes User Group, they can bind Harness role only that prefix with “abc” If the User Group Role binding is created with Non abc role – block the action Restrict UserGroup SAML binding with only harness idmart group When app team creates Harnes User Group, they can bind SAML SSO group that has abc-gp If the User Group SAML SSO binding is created with Non abc-gp – block the action OPA policy that should not allow users to delete a set of variables that we are creating by default in every project, Only Admins could.

There is no feature for propagating services in child pipeline from parent pipeline. If no, what is the alternate way we can have to propagate service and artifacts from parent pipeline to child pipeline? Let's say I have one stage(notification) in both pipeline(parent and child). We are propagating services for each stage in the pipeline. So, during runtime I want to choose service and artifact path for parent pipeline and same should apply to child pipeline.

While testing in the OPA testing terminal the whole yaml including child pipeline can be seen. As part of the end pipeline we are using a stepgroup under stage. So, in the yaml I can't find the templateRef and template.versionLabel related fields.

We'd like a method to be able to show only the "latest" of a particular set of values. For example, if we are investigating the overall pipelines in our environment and want to see the most "latest" executions of each pipeline, we cannot do so. Those latest executions could happen hours to minutes to months ago. It would be a variety of executions. We just want to pull the most recent

Are there instructions for getting dependabot to update image references in harness yaml templates/pipelines? I note dependabot supports k8s already and the functionality is very close, both follow the image: foo/foo:1.1 format