New workflow
Release notes
New features
- Introducing the new workflow: First, the user needs to add the Dev Env descriptor to their local catalog. This can be achieved by cloning a catalog Dev Env, initializing a project, importing the Dev Env descriptor shared by someone, or creating a new one. As a next step, the user can further tune the Dev Env. Finally, the Dev Env installation can be done with a single command.
- A Dev Env's required tool images can be removed with the
uninstall
command. The local Dev Env descriptor can be deleted from the local catalog with thedelete
command. - CLI autocomplete added.
- A single tool in a Dev Env can be modified directly with the
modify
command without opening the Dev Env settings panel. - Timeout value for the HTTP requests is coming from the config file.
- A Dev Env can be assigned to a project with the
assign
command. - If a project already has a Dev Env assigned, the assigned Dev Env can be initialized with the `init˙ command.
- The
clone
command now can be used to create a local clone of a catalog Dev Env descriptor. The original functionality, creating a local copy of a local Dev Env, is now available under thecp
command. - Host management added.
Documentation
- README updated.
- Contribution guide updated.
- PR template updated.
- Documentation for the new workflow added.
Disclaimer
After upgrading your DEM from v0.2.X or earlier, the dem install
command must be issued for all the locally available Dev Envs. The command will simply set the installed state of these Dev Envs to true.