Feature Requests

As part of creating ServiceNow change requests in a CI/CD pipeline, we've been making several GET API calls to ServiceNow-- to look up existing Releases, CMDB Configuration Items, Change Requests, and Assignment Groups. Currently, we're making manual HTTP requests to the API, but it would be great to have a built-in step that uses our existing ServiceNow connector to allow us to retrieve data from different types of tickets.

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.

There is no ability to redeploy without doing a CI build again when a pipeline is deployed to prod successfully. We need to have a ability to redeploy without doing CI in case of cluster repave. State needs to be persisted in order to do that. Currently its supported only when we use “re-run from last failed steps”.

Please make the emails of your recipients box in the notification section of a pipeline able to perform expression resolution. Pipeline -> notify -> new notification -> on failure -> email -> <+expression of user email based on who approved something in the pipeline> <+ pipeline.stages.Run _terraform.spec.execution.steps.HarnessApproval_1.output.approvalActivities[0]. user.email > This could be as easy as removing or changing a regex validation for the box.

Ability to map ConfigMaps (items) as a volume/files in ContainerStep This will allow to use standard container images to execute bash/python scripts using ContainerStep without building and maintaining a custom image.

Please update the ServiceNow Plugin to be compatible with ServiceNow Xanadu. Since it is not compatible, it cannot be installed with this version of ServiceNow

We would like to store pipeline.yaml in an external git in order to have a clear history of changes that are made to these configurations. By default, commits are made back to git using the service user credential defined in a git connector, but our company's engineering standards require all commits in our git instance are done by a real person, not a service user. The "Providers" functionality allows harness to commit as an individual, but there is no way to force that a user has a provider access token configured. We would like a way to enforce that pipelines cannot be saved in harness unless that save will be done using an end user's access token.

While executing the pipeline, how to hide the code/script being displayed in the execution logs.

Service was initially onboarded with INLINE as the storeType and later moved to REMOTE. However, the audit logs do not capture the change from INLINE to REMOTE.

Remove the 2-step limit from the upload files as Runtime Input feature. Several upload steps per pipeline are needed to validate individual tests. 100 MB limit is acceptable, but needs to be spread out across multiple upload steps, not just two.