What should the workflow for removing a config be?

[reidsunderland]

The proper procedure for removing a config using sr3_tools isn't clear.

[reidsunderland]

sr3_remove only removed one file at a time, and simply removed the config from the node.

The built in sr3 remove supports multiple configs and removes the corresponding .cache directory for the config.

I updated the tools to:

• Disable sr3_remove and inform users who try to use it to use sr3d remove instead
• Update sr3d to make remove usable, and update the Git repo at the same time.

The correct workflow for removing configs is now:

sr3d cleanup component/config ....
sr3d remove component/config ....

[petersilva]

to remove > 1 config requires the --dangerWillRobinson flag... fwiw...

[reidsunderland]

Added support for --dangerWillRobinson with https://github.com/MetPX/sr3_tools/commit/72c62b83cc2d4689ae042ad63923886ada6215f6

if the user doesn't specify --dangerWillRobinson, it still runs the remove on the nodes, where sr3 gives an error.

$ sr3d remove flow/hydro_quebec_http shovel/copy_ALPHA
dev01:
dev01: 2023-10-18 17:21:05,448 64002 [ERROR] root remove specify --dangerWillRobinson to remove > 1 config at a time
dev02: 2023-10-18 17:21:06,777 27309 [ERROR] root remove specify --dangerWillRobinson to remove > 1 config at a time
dev02:

[reidsunderland]

This is done. sr3d remove ... works, including with --dangerWillRobinson