Feature Requests

Currently Nested chaining is not supported which means pipeline stages cannot call a pipeline that has chained pipeline stages in it. Need to have the ability to create Nested pipeline chaining

The App-of-Apps pattern is widely adopted in ArgoCD to orchestrate applications across environments and clusters. We require the ability to define a root “App-of-Apps” in Git that can manage child applications targeting different clusters and namespaces. Currently, Harness GitOps does not support this pattern natively for multi-cluster use cases. Requested Capability: Native support in Harness GitOps for multi-cluster deployments in the App-of-Apps pattern.

We want the ability to create webhooks using the Terraform Harness Provider

Currently, Harness does not support Harness expressions in OPA policies, which limits the ability to differentiate between a manual run and a rerun within the policy itself. It would be beneficial to have this support to enhance policy differentiation capabilities.

Hi Team- We would like to request support for Test Intelligence in Step Templates. Currently, when attempting to create a Step Template from a working Test Intelligence step in a CI pipeline, we receive validation errors such as: body: is missing but it is required pipelineStatus: is missing but it is required -failureStrategies: is missing but it is required -when: object found, string expected -infrastructure: is missing but it is required

Currently, the remote flow works correctly for the default branch. However, we need the OPA policies to work on non-default branches as well.

Hi Team, I need help for configuring argo rollout for our deployment. do we have any feature/options available apart from this doc https://developer.harness.io/docs/continuous-delivery/gitops/argo-rollouts/argo-rollouts-overview/ it would be better if we could connect over the call and discuss. Thanks

Hi Team, Would request to enable this feature feature is behind the FF PIE_TAG_BASED_ACCESS_TO_PIPELINES. I see from the documentation that it has to be enabled https://developer.harness.io/docs/platform/role-based-access-control/tag-based-rbac-for-pipelines/ Once this is enabled please confirm. Thanks

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.

Hello all, could you please enable this feature flag on our account PIPE_STORE_TEMPLATE_REFERENCE_SUMMARY_PER_EXECUTION Account ID: 4vHVRSnRT9K-mOIbeIOFmg Before we turn it on: May I ask you about the User experience impact of this change, will the user have any impact on his experience using Pipelines?