Feature Requests

Currently STO module isn't listed in the selection of resources within resource group. Although the users have the necessary roles assigned to the view entities within STO, they will need have "all" the resources selected in the resource groups if not they are presented with a 403 forbidden error on the UI. Having granularity to select STO objects will be beneficial.

There is no ability to redeploy without doing a CI build again when a pipeline is deployed to prod successfully. We need to have a ability to redeploy without doing CI in case of cluster repave. State needs to be persisted in order to do that. Currently its supported only when we use “re-run from last failed steps”.

We need the ability to configure an OIDC connector that uses a workload identity pool and service account in a different project from the cluster we want to deploy to. Our IAM standards require service accounts to be in their own project, so it's essential to provide the project we want to target in the infrastructure definition. This feature would greatly enhance our deployment flexibility.

Currently, only fixed values are supported as allowed values of a runtime input. The idea is to populate a list of values in one step that could be used in the later step as the execution runtime input allowed values. Then, the end user could have the option to choose those allowed values that populated from the previous step as part of the execution runtime input.

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.

Code Owners should be reviewers so that they can be informed about changes to Repos under their ownership.

User would like to be able to impersonate other users when using the UI.

Customer is requesting a native step in Harness for downloading artifacts from Google Cloud Storage (GCS), similar to the existing "Upload Artifact to GCS" step. Currently, users can achieve this functionality using the GCS Drone plugin. However, they are looking for a solution that supports OIDC authentication to eliminate the need for manually inputting service account tokens into the pipeline.

Currently the prisma STO step is marked as success even if "Vulnerability threshold check" result is "failed". We need to ensure that the execution fails if the "Vulnerability Threshold Check" fails.

Ability to map ConfigMaps (items) as a volume/files in ContainerStep This will allow to use standard container images to execute bash/python scripts using ContainerStep without building and maintaining a custom image.