Promotion/demotion ability for Templates
long-term
A
Ambitious Swan
We think it would be beneficial to allow for promotion/demotion of Templates between Project/Org/Account level. This will allow users to copy down Account level templates which shouldn't be edited to allow them to edit and customize for their needs, then promote back up to Org/Account level without potential interruption to other projects/pipelines.
Log In
Autopilot
Merged in a post:
Provide option to promote template from Project Level to Org/Account level templates
V
Venetian yellow Caribou
As part of Harness utilization, many teams build custom templates and interested to contribute to the Platform so that the other BU's can use the same
Autopilot
Merged in a post:
Template promotion from project to Account
V
Venetian yellow Caribou
To promote inner sourcing in our organization, we would to enable option to user to promote templates from project level to account level as community templates. Right now i dont see an option for the same.
As we are many BU and Shared services it is must we need some way to promote templates.
Autopilot
Merged in a post:
Cloning templates across projects
R
Ruby Octopus
We require the capability to copy or move account-level templates to a project, as well as the ability to copy or move templates from one project to another.
Rohan Gupta
Merged in a post:
Change template scope
H
Horizon blue Dormouse
Occasionally, I have created templates at the project level that I would like to transfer to the org/account level. I can recreate the new template at the new level (if I change the identifier or remove the original) but it would be nice to be able to transfer it wholesale between abstractions if possible.
Rohan Gupta
marked this post as
long-term
I'm thrilled to inform you that your idea has been carefully reviewed and evaluated by our product team. We are excited to announce that it has been taken into our backlog.
We will keep you updated on the progress and let you know as soon as it is available.
Should you have any questions, suggestions, or thoughts you'd like to share, please feel free to add more to this feature request.
Rohan Gupta
marked this post as
under review
Rohan Gupta
Hi Ambitious Swan what is preventing the user from making a copy of the template making tweaks and then opening a PR to merge the suggested changes in? That's how other user's are managing templates today and performing changes.
They copy the template or make a new version of the account level template, make changes to it and then open a PR on the template file to accomodate the changes if managed in Git.
In Harness Versioning it's just testing the version and then promoting it to stable
I
Implicit Squirrel
Rohan Gupta: The way I viewed this is really ease of use. We can certainly do all sorts of copy/paste of the Yaml files, but if you can make it super easy for users, that will keep them within your platform and want to use it, vs going to vscode or other tools for this.