Feature Requests

Step in CI stage to upload artifacts to our Nexus artifact repository similar to 'Upload Artifacts to JFrog Artifactory' step.

We would like to extend the data retention period for the cd module in the NextGen platform to 12 months. We currently have the same period in the FirstGen platform.

We are using several templates at the org level (steps and pipelines). Projects are consuming the pipeline templates and often need to be reconciled when variables or other elements in templates change. Is there a way to programatically (API endpoint, Terraform) reconcile pipelines after templates have been updated. Right now the only way I can see doing this is through the UI and manually clicking through pipelines to see which needs to be reconciled. This is adding a lot more time to using templates. Why can't the pipelines that are calling the templates just render the template at run time? I am doing a very similar approach on GitHub actions and never need to inform my upstream workflows to update themselves because a template changed. On checkout, my actions use the template ref provided. I'm guessing because the templates do not live in an SCM system, that the Harness pipeline that is referencing the template needs to store a cached copy of the template? The whole reconcile pipelines does not make a lot of sense to me. I want the template to drive what is happening in the pipeline and not have to constantly make sure the "caller" pipeline is caching the template...or whatever is happening under the hood. I can understand locking a pipeline to a known good template, but isn't that why there are template versions? Which is a whole different topic.

Currently if we try to modify pipelines and choosing branches from the dropdown, it lists only 20/30 branches depending on the git provider. Anything above is not even searchable. The expectation is to return the first X results matching search string

Please can improvements be made when using the specify infrastructure field during deployments. Currently the list is not sorted alphabetically can this be ordered in this may to make it easier to search. A further request would be to make this field searchable, giving the developer the ability to start typing and results come back, for example if a dev would type "sma" the drop down would filter alphabetically smapiv1 smapiv2 and so on and so on.

We want the ability to deploy applications and execute jobs on Google Cloud Run. https://cloud.google.com/run/docs/overview/what-is-cloud-run

We see harness logs are exported as plain text on the delegate pods. Please help us to change the delegate logging format to JSON instead of plain text. This is needed for us create dashboards in ELK based on index. example logs : 2023-09-04 14:38:50,134 [task-exec-4] INFO io.harness.delegate.task.scm.ScmDelegateClientImpl - scm channel successfully shut down [accountId=<actid>, taskId=a2efLl5kQCOjw_J3ZCitHw-DEL] 10.70.125.125 - - [04/Sep/2023:14:38:55 +0000] "GET /api/health HTTP/1.1" 200 74 "-" "kube-probe/1.24+" 1 2023-09-04 14:39:00,278 [AsyncHttpClient-3-1] INFO io.harness.delegate.service.DelegateAgentServiceImpl - New Task event received: {"eventType":"DelegateTaskEvent","accountId":"<actid>","delegateTaskId":"m6sv67ngT8mcNj67SuV1eQ-DEL","sync":true,"taskType":"CAPABILITY_VALIDATION"} 2023-09-04 14:39:00,311 [task-exec-5] INFO software.wings.delegatetasks.PerpetualTaskCapabilityCheckTask - Checking Capability: HttpConnectionExecutionCapability(capabilityType=HTTP, url= https://github.com/harness.git , headers=null, host=null, scheme=null, port=0, path=null, query=null, ignoreRedirect=false) [accountId=<actid>, taskId=m6sv67ngT8mcNj67SuV1eQ-DEL]

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

Dear Harness Support Team, I hope this message finds you well. We would like to request the activation of the feature flag named CI_GIT_CLONE_ENHANCED for our Harness account. We are particularly interested in this feature to take advantage of the improved Git clone operations in our Continuous Integration (CI) pipelines, which include support for Git LFS, Fetch Tags, Sparse Checkout, Clone Submodules, Clone Path Customization, and additional Pre-Fetch Commands. Please enable this feature flag at your earliest convenience. If you require any additional information from our side, please do not hesitate to reach out. Thank you for your prompt assistance. Best regards, Anurag

Untagged resources. It would be nice to see account, service, and usage type to help uncover what the untagged resource is related to. We tag resources with StackID which helps us uncover the owner. If a resources cannot be tagged having the account, service or usage type would help find the owner. There is a field in AWS for who created the resource but that may not always be helpful.