Feature Requests

Dashboard for listing all the components across the all projects so that user can search for components at account level and a dashboard for listing all pipelines that have SBOM component violations

I would like the Pipeline Executions explore in the dashboards to be enhanced with additional data points. Can the overall pipeline error message be added for failure cases? In addition, I would like to see the following details for Stages and Steps details that were executed: Type (e.g. CI) Duration Status Templates referenced (project/account scope, name, version) Language (for CI) Bitbucket connector utilized Repository Name Environment Type (for CD) Services Deployment Type (for CD) Stage/Step Error Message ID used to deploy (for CD)

Currently, Test Intelligence does not work with pytest-xdist. We would like to see support for this

Similar to the CD module user would like to have the Approval as a CI step.

With nested pipelines, we have an ability to override the pipeline input --> codebase settings like: Git branch , git tag and git pull request can be defined as either fixed value or an expression - that is ok. Clone depth can only be either a fixed value or an input. We can't use expressions to specify clone depth - not ok. Please add an option to set clone depth through an expression.

I would like to use utilized cost, forecast cost and budget cost to calculate the difference between forecast and budget inside dashboards.

We would like Harness to seek out methods to reduce the Windows Drone-git image size. Currently, it exceed 2Gb, leading to long initialization processes. This may be the nature of a windows image, but anything Harness can do to reduce the size would be helpful

We need support in adding projected volumes under the Infrastructure section. We attempted to add it directly to the pipeline YAML, but it failed during the initialization step. Here is the content we need to include in our YAML file: name: aws-iam-token projected: defaultMode: 420 sources: - serviceAccountToken: audience: sts.amazonaws.com expirationSeconds: 21600 path: token Reference: Harness Deployment Pipeline https://app.harness.io/ng/account/aCdxAwyBQE6h7zSB7d9fBQ/all/orgs/Engineering_CI_by_[…]/deployments/GK_n7bF-RjqEEnZGA0Wecw/pipeline?storeType=INLINE Could you assist in resolving this issue?

Description: FIS Global has requested an enhancement to the Container Security Context settings when configuring a step group. Currently, there is an option to specify "Run as User." They would like an additional option to specify "Run as Group" to provide better control over permissions and execution contexts within containerized environments.

In IDP, we are currently able to see PR's from Github and Harness Code. Please extend this capability to BitBucket