There is also new option added to block/unblock command to prevent accidental termination of objects such as machines, services, units and relations.
When this block is desired, the users can run
juju block remove-object
This will block all termination commands from running successfully. Current juju termination commands could be any of these forms - "juju remove-machine... ", "juju remove-service... ", "juju remove-unit... ", "juju remove-relation... ", "juju destroy-machine... ", "juju destroy-service... ", "juju destroy-unit... ", "juju destroy-relation... " and "juju terminate-machine..."
When users intend to remove machine, service, unit or relation from the environment where there is this block, they will have to explicitly unblock remove-object operation by first running
juju unblock remove-object
Note that forcing machine removal will also by-pass this block. However, this is one of the assumption that I have made.
There is no "force" to by-pass when removing service, unit or relation.
There is also new option added to block/unblock command to prevent accidental termination of objects such as machines, services, units and relations.
When this block is desired, the users can run
juju block remove-object
This will block all termination commands from running successfully. Current juju termination commands could be any of these forms - "juju remove-machine... ", "juju remove-service... ", "juju remove-unit... ", "juju remove-relation... ", "juju destroy-machine... ", "juju destroy-service... ", "juju destroy-unit... ", "juju destroy-relation... " and "juju terminate- machine. .."
When users intend to remove machine, service, unit or relation from the environment where there is this block, they will have to explicitly unblock remove-object operation by first running
juju unblock remove-object
Note that forcing machine removal will also by-pass this block. However, this is one of the assumption that I have made.
There is no "force" to by-pass when removing service, unit or relation.