Feature Requests

I would like Dark Mode so my eyes don't scorch when using the UI late at night

Problem Statement Currently, personal API tokens created by users in their profile settings can only be deleted by the token owner. This creates a security control gap where administrators have no ability to revoke a user’s API access in scenarios where immediate token revocation is necessary (e.g., compromised accounts, departing employees, security incidents, policy violations). Current State Service account tokens: RBAC controls exist for deletion User profile tokens: Only the user can delete their own tokens No admin override capability exists Requested Functionality Enable account administrators and authorized service accounts to delete user API tokens created at the user profile level. Specific Requirements: Admin users should be able to delete any regular user’s API tokens Service accounts with appropriate account-level permissions should be able to delete regular user’s API tokens Should maintain audit trail of token deletions (who deleted, when, which token) Use Cases Security Incident Response: Immediately revoke tokens for compromised accounts Offboarding: Ensure complete access revocation when users leave Compliance: Enforce token rotation policies Policy Enforcement: Revoke tokens that violate security policies

I would like the ability to organize Account Level Templates in a folder structure, currently with over 330 templates it is unwieldy to use. Ability to set permissions would be ideal, but at least the ability to sort in GUI by folder would be very beneficial.

Can support for mermaid diagrams please be added when rendering markdown in Code Repositories?

When running a child pipeline using parent, in the OPA evaluation we do not have any details which can tell if the pipeline is triggered by parent or manual. Adding this info will have fine grained OPA evaluation and more control.

So we have input StartDeploymentFrom and the selection of that is the env present in the pipeline. Now, what we need is to show two vars, SkipCanary and SkipTestExecution only if the StartDeploymentFrom is selected as prod-*, otherwise the var would have the default value and does not show in the UI. This would help us make things simple for the devs, as they need to provide minimal inputs and if the option is present then only it would select the other input. Currently it creates the confusion, in the sense that, user changes those vars but it does not have any effect because its not hotfix and nothing should be skipped, so if the user does not see that in the first place, then no confusion is there. For us this is one of the requierment, but I do believe that other users and org would also have the similar requirements. This ticket seems similar but in rejected state - https://ideas.harness.io/feature-request/p/dynamic-runtime-inputs

We would like the ability to reference IACM Workspaces via tagging when creating Resource Groups. This will allow us to more effectively apply RBAC permissions and governance for workspaces between project within our Harness environment.

We'd like the ability to create sub-folders for Perspectives to keep them organized. Currently with over 500 Perspectives and growing, only having the one layer of folders does not allow for proper management of Perspectives.

Move inline triggert entities to Git?

Currently, the Prometheus connector only supports username and password authentication. We use Prometheus with Azure managed identity and would like to get the added support for the same.