When cloning a workspace today, the contents of the workspace bucket are not cloned, with the exception of the "/notebooks" directory.
This is an understandable default, as workspaces for running workflows can have a lot of data stored in the Cromwell submission execution directories, which you would not typically want to clone.
However, it would be nice to be able to publish a workspace and have a clone of it be a complete clone. The workspace bucket could contain sample data or README files or PDFs of papers.
Options for this today are to put these files:
- into the /notebooks workspace bucket path.
- into a Google bucket in a non-Terra project (and just reference them from the workspace).
- into the workspace bucket and give instructions on how to reference/copy
any of these approaches are okay. Each has its trade-offs.
One approach to implementing this would be to have a dialog when cloning a workspace such that the user could select which workspace bucket folders to clone.
Please sign in to leave a comment.