Feature Requests

We'd like the ability to edit git_details for Environments in the Terraform Provider.

User wanted have the support of Test Intelligence for Javascript/Typescript.

Gitops Applications landing page should be refreshed as new apps get created in background

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, when rerunning a pipeline execution, the system utilizes the latest pipeline definition but retains the original inputs. However, this behavior makes it difficult to reproduce past pipeline executions, which is a recurring frustration for engineering teams. We are requesting the ability to rerun a pipeline with both the original pipeline definition and the original inputs, ensuring true reproducibility of past executions. The feature could be implemented as a configuration option that allows users to choose whether to rerun with the latest or the original pipeline definition. For our account, we would prefer this configuration to default to the original pipeline definition. This enhancement would greatly improve debugging and provide more reliable historical execution reproducibility. We are hoping to have this feature included in the roadmap for Q4.

In our organization, we use a custom manifest script with Helm to dynamically select repositories based on pipeline variables, such as using 'helm-prod' for release builds and 'helm-dev' for non-release builds. We need similar functionality for DB DevOps to dynamically pull schema artifacts from different Artifactory repositories. This feature would greatly enhance our deployment process and align with our current practices.

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.

User would like to be able to impersonate other users when using the UI.

Currently we do not consider the delegateSelectors while sending the notifications via delegate. This is a request for the Notification Service to honour the DelegateSelector config, if the notification is configured to be sent through Delegate.

Needed ability for the docker delegate to upgrade automatically.