Feature Requests

Early new year App Store will stop accepting apps build on previous SDKs as IOS sdk 18 has been released on September 16,2024. Currently, Harness supports Xcode 15 on IOS sdk 17 as per following documentation: https://github.com/wings-software/harness-docs/blob/main/harness-cloud/macos-14-Readme.md

Can you please enable Flexi templates on sokpxFqZQgKJR8hG7DlZXQ

please add CI_GIT_CLONE_CONTAINERLESS

Does sonarqube extraction scan supports pulling pull request scans? Assuming that we enable the API access to the ADO Connecters, how should we pass the pull request id to the sonarqube scan step? If the extraction scan does not support the pull request scan, is there a way to pass the specific analysis id and have it pull that?

In our pipeline, the Jira plugin errors out when the 'description' field exceeds 255 characters. This is problematic as our commit messages can be quite long. It would be beneficial if the plugin could either truncate or ignore descriptions that exceed the character limit, rather than erroring out.

The Harness gitops-agent helm chart has a feature to automatically upgrade itself. However, it doesn’t respect using private registries or internal proxies to DockerHub and there appears to be no way to configure it to do so. We want to be able to leverage the auto updater job while still using our private Artifactory to proxy to DockerHub to get the images.

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.

We have a Shell Script Step that sets some output variables as secrets and we are not able to refer it in the same container step.

I would like the ability to create banners via the API. This feature would streamline our processes and allow for more efficient management of banners across different accounts.

For pipeline Freeze window: Admin users should get a notification banner when running pipeline in freeze window same as other users. 2.Admin users better yet be blocked like normal users but then have an explicit option to bypass, similar to an approval gate or something on a CD pipeline