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?

Problem Teams migrating from Jenkins lose the ability to push code quality reports (FindBugs, PMD, Checkstyle, Coverage, CPD) directly to pull requests with delta comparisons against the base branch. Harness CI supports basic pass/fail status checks, but cannot post detailed report content to the PR interface. Requested Functionality Native integration to post code quality results directly to PRs in GitHub, GitLab, and Bitbucket: PR Summary Comments — Post violation counts, coverage delta, and quality gate status Inline Annotations — Flag specific lines where violations were detected Delta Comparison — Show only new issues introduced vs. base branch Configurable Thresholds — Define pass/fail criteria (e.g., fail if coverage drops >2%) Report Format Support: Coverage — JaCoCo, Cobertura, Istanbul Static Analysis — PMD, Checkstyle, SpotBugs, ESLint, SARIF Functional Tests — JUnit XML (Go, Python, Scala, Node.js, Java) Business Value Consolidates quality data where reviewers already work Reduces context switching to external dashboards Enables quality gate enforcement before merge Provides Jenkins parity for enterprise migrations Reference Implementations Jenkins Warnings NG Plugin SonarQube PR Decoration Codecov PR Comments

Allow Harness to retain the state of previous stages, enabling users to make decisions such as re-running only failed test cases. Users should have the ability to re-run failed stages or tests directly from the UI, or via an out-of-the-box solution

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.

Pull New Code Coverage from Sonarqube API and add as output variable Sonarqube

Bitbucket’s Required builds merge-check expects the build status payload to include a parent field that exactly matches the required-build key configured in the repo. Harness does not set this field by default, which is why the check isn’t being satisfied even though the build shows successful. Please add the parent field while sending the build status so that the required build merge checks can detect it.

Currently, OPA is not supported for projects. Only Pipelines, templates, feature flags, and connectors are supported. It would be useful to add Policy at a user level to do things like deny applying permissions directly or enforce naming conventions.

Currently, when a group exists in both Azure AD and Harness, but certain users are found only in Azure AD, forcing provisioning from Azure AD fails. This occurs because Azure identifies the user as already present, even though it is not in Harness. We propose a feature to enable account administrators to force-delete users or groups that were provisioned via SCIM. This functionality would allow for a clean refresh of data from Azure AD, resolving synchronization issues without manual intervention.

Right now harness only allows to run shell script only at run time. is it possible enabling python script also to run at runtime.

Right now Harness allows only shell script to run on runtime. is it possible to add python script also to run at runtime in similar way like shell script? Please find attached screen shot