BlueShieldCA has the following use case: Users create a release from a template and proceed to enter values for several dozen required variables on the "Create new release" panel. In the event of a release failure due to an incorrect folder, bad input, or any other reason, the release is aborted and the user starts over again from the template. Users do not have permissions to edit variables during release execution because many of them pertain to Ansible provisioning -- edit access to the release is limited in order to prevent unauthorized requests to Ansible.
But having to re-enter all the inputs for another release is tedious and inefficient. From what I've seen there isn't any way to populate the "Create new release" panel since it is presented in the GUI before the new release is actually created, and thus it is not accessible by any of the methods in releaseApi.
Do we have a way to influence the data seen on this panel? Ideally, the user would point to another release derived from the same template, instruct the GUI to populate the show-on-create-release-form variables from that other release, then edit the few values/items that were wrong before creating another new release.
by: Tony H. | 6 months ago | Templates & Releases
Comments
Thank you for the idea. We will seek broader support from the customer community.
Similar idea with slightly different use case: https://ideas.digital.ai/devops/Idea/Detail/4402
We are planning to incorporate this change in the upcoming 25.x releases. Once our planning is finalized, we will provide an update in this idea thread. Thank you for your valuable input!