Feature Requests

Hi, I have a pipeline that reads the secrets (username,password,port) for connecting to the servers. These servers are grouped by environment. Ex: Environment A123 has servers server1, server2, server3. Currently, I define the secret like env123_ser1_username, env123_ser1_password. It will be best, if there is a functionality to group the secrets by environment env123.

We recently had our upgrader job break our delegates because the override we specific using this api, ( https://apidocs.harness.io/tag/Delegate-Setup-Resource#operation/publishedDelegateVersion ), expired. This broke our delegates because our runner clusters do not have internet access, and the upgrader set the delegates to pull the public image, sending our delegate workload into a imagepullbackoff loop

Not allowing organizations to delete until all projects are deleted inside it.. This feature should be applied to harness organizations to avoid deletion of orgs without cleaning up projects inside it. same as s3 bucket in AWS.

There should be some option to configure the notification schedule like right now it only sends one notification which Ops team can easily miss, so its good to have multiple notification may be every day or after 5 hours etc but we can't configure this right now so I request you to implement this feature.

The API for LDAP sync-group is currently undocumented, which poses challenges for users trying to implement it effectively. It would be beneficial to have comprehensive documentation available for this API to ensure users can utilize it correctly and efficiently.

If delegate pods were scaled down then as part of delegate notification its not working although configured as below: https://developer.harness.io/docs/platform/notifications/manage-notifications/ Also we can see as part of notification rule we can not use delegate tag and need to pass/select the delegate name, as with tag notification is not working

we can use harness smtp.

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.

Need Delegate_task_failed metric in case of script failure or error for more details

Currently, when viewing "All Dashboards," it’s difficult to determine which dashboard belongs to whom, especially when the same dashboard name is used repeatedly during cloning. Adding the folder name where the dashboard is located would provide better context and help users identify the origin of each dashboard at a glance.