Feature Requests

We manage and release all versions of our repos using a combination of semantic versioning and git tags. This means our versions are stored in tags, not branches. Can we have templates versions extended to support tags in addition to branches?

Import multiple template versions with terraform provider

Description: Currently, the Harness container step does not provide an option to configure resource requests directly from the UI. This feature is controlled from the Harness backend, limiting users' flexibility and control. Requirement: We need an enhancement in the Harness UI that allows users to configure resource requests (CPU and memory) for the container step. This configuration should be optional, and if no specific values are provided, the system defaults to predefined settings. Use Case: This feature is crucial for running JMeter or other performance tests as part of the continuous deployment (CD) process. Performance tests often require specific resource allocations to ensure accurate and reliable results. Without the ability to configure these resources, users may face challenges in optimizing their testing environments, potentially leading to inaccurate performance metrics and inefficient resource utilization.

Gathering data from steps to pass from stage to stage can be confusing for developers consuming templates. An ability to pass this information into a stage level output similar to how stage variables work for input would be extremely useful. An example could be a complex stage which includes build of a container image could pass the full image path and separately pass the registry, image name, tag and SHA so these are more easily passed into the deploy stage for selection of the image to deploy.

Create an EKS add-on that deploys the Harness GitOps agent. This will allow to seamlessly deploy GitOps agents to cluster without requiring extra steps from the end-user.

Create an EKS add-on that deploys the Harness Delegate related component. It would simplify private cluster setup and limit manual steps to set up connectivity between Harness and EKS.

Upgrade MacOS image Xcode 16.3 for CI builds

Currently the expression suggestion does not show up in the email body. However, the expression resolution works fine and the YAML view still provides the suggestion when the body content is edited. Providing the suggestions for email body shall provide better user experience.

I want to dynamically generate sections in the IDP workflow based on field values selected in the first title. Currently, the scaffolder doesn't support conditional logic to show or hide entire steps or sections. It would be beneficial to have this feature to enhance the flexibility and efficiency of the workflow.

We would like to leverage account, org, and project level variables, but to be able too override them at the environment, service, infrastructure, and service+infrastructure level