Feature Requests

We are using Github maven package registry instead of nexus for dependency management, so were using pipeline chain from library repo to service repo pipeline which is not working anymore because service pipeline has one more regression test pipeline chain

Adding values beyond those defined in the dropdown for a variable - I am able to select values from the dropdown, which is exactly what I am looking for. However, in addition to selecting a value from the dropdown, the user should also be able to enter a value manually. The user should be able to either select a value from the dropdown or enter their own value. Example: <+input>.default(varaible_name).allowedValues(aaaaa,bbbbb,cccccc,ddddd,) Once you implemented can you inform me

I used Split.io extensively in my last company. I joined a new company and recently had intended to propose the use of Split.io feature flagging. Finding out it has come under the umbrella of Harness I decided to see if the Feature Flag offering is the same only rebranded. but it seems it's significantly worse and more limited. The create/edit experience is not nearly as powerful and user friendly as Split's. Where can I access Split.io 's feature flagging capabilities under Harness?

Hi Harness Support, We need your help to enable the Gcloud Run plugin on this Harness Account, where we want to create Pipelines for the Cloud Run deployments. This Plugin will be helpful for us to perform the CICD to our Google Cloud Run for the applications deployments. Cloud Function is already available, but want to get Cloud Run option also. Let me know if any details needed from our side.

I would love to see a way to hide or override the "Loading..." that is appended to the DOM during Feature Flag initialization (React library). We have our own loading screen, so the plain <p>Loading...</p> is quite out of place in our UI when it shows up and requires unnecessary CSS overrides to hide it from view. I honestly believe that the loading message should be hidden from the UI by default, but I would settle for being able to pass in a component that would show up instead. Currently overriding it like this, which feels a bit awkward: useEffect(() => { for (const p of document.querySelectorAll('p')) { if (p.textContent?.includes('Loading')) { p.classList.add('hidden'); } } }, []);

Enable feature flag for CDS_AWS_LAMBDA_DISABLE_DOUBLE_VERSION_PUBLISH

We had multiple version publications we got update that June 19th it will be released. We are raising one request to enable feature flag

In the below document it talks about how SCM status updates are automatically created for commits. It would be good to have an option to toggle this functionality on a per pipeline or per input set basis. https://developer.harness.io/docs/continuous-integration/use-ci/codebase-configuration/scm-status-checks/

Hi team, this is ticket is part question/part feature request. we have many feature flags stored in "Feature flags" project and we are planning to enable git sync for them. however, we realized that 1 project can only be synced to a single yaml file, which results in a massive yaml file that can be difficult to maintain. we are wondering if the git sync allow wild card matching to pull all yaml files within a folder (ideally separated by teams) to allow easier management. thanks!

Current Behavior: When a feature flag (FF) is toggled via a pipeline, the audit trail records the action as performed by "SYSTEM" rather than capturing the actual user who triggered the pipeline. Feature Request: Can we enhance this functionality so that the audit trail reflects the correct username of the individual who triggered the pipeline that resulted in the FF being enabled?