I often need to deploy a template that has a large number of mirrors that I want to detach so that the changes I make to that template instance don’t get made across the mirror network.
Currently it doesn’t look like I can do that en mass. I have to click on the menu and then the command for every single mirror.
Can we get a menu command to detach mirror(s) when multiple mirrored nodes are selected?
Detach one instance, make your changes and use it going forward as you don’t want the changes in the old mirrors?
@renkiohen why the template has mirrors in the first place?
Do you use the #template and the new slash command "add template "?
The mirrors inside the template represent a database that I want to be in a certain state. Template instances should reflect the current state of that database. But during the use of a template instance I need to change the mirrored items because of how I’m using each instance. However I don’t want those changes to affect the original database.
This feature would allow me to deploy template instances in the image of the current state of the database, change the instance as needed, and still maintain the state of my OG database.
Perhaps something like this as a workaround.
I’ve noticed that copying mirrors deploys them as detached which helps. So arguably the workaround here could be, instead of deploying the template and detaching mirrors, just open the template, mass select the mirrored items and copy them into a new manually created instance.
One way is to Export the parent node as OPML. Then copy and paste the OPML. All mirrored items within the pasted node hierarchy will be detached from the mirror.
Sorry for the late response, just hoping it will be helpful to someone.