You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, exported container JSON files can only be imported in an existing container's Version screen. This means that to add a new container that is a duplicate of an old container, you must take these steps:
On the Manage Containers screen, click create a new container
Name the container
For this container, open the configuration
Go to versions screen
Click on Import
add the JSON file and click "overwrite"
Suggested workflow:
on the Manage Containers screen, click Import container (opens screen as mocked up attached
name the container
add the JSON file, and click Import.
While the sequence of required steps is "only" 3 steps shorter (a 50% reduction though), it simplifies the workflow by a lot. It's possible that many users are not familiar with this feature, because it's somewhat hidden away in the versions screen.
My suggestion would be to maintain the current functionality as well, as it still allows people to overwrite existing containers which can be helpful for other use cases (such as restoring a backup).
The text was updated successfully, but these errors were encountered:
Currently, exported container JSON files can only be imported in an existing container's Version screen. This means that to add a new container that is a duplicate of an old container, you must take these steps:
Suggested workflow:
While the sequence of required steps is "only" 3 steps shorter (a 50% reduction though), it simplifies the workflow by a lot. It's possible that many users are not familiar with this feature, because it's somewhat hidden away in the versions screen.
My suggestion would be to maintain the current functionality as well, as it still allows people to overwrite existing containers which can be helpful for other use cases (such as restoring a backup).
The text was updated successfully, but these errors were encountered: