<!--- Provide a general summary of the issue in the Title above --> ## Expected Behavior Add CLI entrypoint for easy renaming: `$ happi rename at2l0 at2l0_foobar` or perhaps `$ happi rename at2l0=at2l0_foobar at1k4=at1k4_foobar` This would update the 'name' field, the internal '_id', and the parent JSON db key for that backend ## Current Behavior I believe this is how it'll work as-is, but correct me if not: * Renaming can potentially be done with `happi edit` * But then `happi repair` (post #327) will reset the name to the id in the case of the JSON backend * This leaves the only option for renaming to edit the JSON file ## Possible Solution Add new `rename` command and fix up `happi edit` The backends may need a corresponding function for renaming
Expected Behavior
Add CLI entrypoint for easy renaming:
$ happi rename at2l0 at2l0_foobaror perhaps
$ happi rename at2l0=at2l0_foobar at1k4=at1k4_foobarThis would update the 'name' field, the internal '_id', and the parent JSON db key for that backend
Current Behavior
I believe this is how it'll work as-is, but correct me if not:
happi edithappi repair(post ENH: Match Name to ID Field #327) will reset the name to the id in the case of the JSON backendPossible Solution
Add new
renamecommand and fix uphappi editThe backends may need a corresponding function for renaming