The use case would be that a user wants to use the newest OBR functionality, but does not want to wipe the entire workspace and start from scratch because the job document structure has changed.
So, the user would call something like obr migrate --folder <path> --from <current OBR version> to essentially overwrite, or create updated versions of, the job documents inside the workspace.
While this might not be the biggest priority right now, it might prove convenient later on. What do you thing @greole ?
The use case would be that a user wants to use the newest OBR functionality, but does not want to wipe the entire workspace and start from scratch because the job document structure has changed.
So, the user would call something like
obr migrate --folder <path> --from <current OBR version>to essentially overwrite, or create updated versions of, the job documents inside the workspace.While this might not be the biggest priority right now, it might prove convenient later on. What do you thing @greole ?