New Features:
- Dependencies: You are now able to specify other devspace projects as dependencies, which will be built and deployed before the current project is deployed. Take a look at the examples for more information.
- Custom Builder: You are now able to build images with custom user-defined commands. See examples for an example. (#534)
- Parallel Image Building: As soon as there are 2 or more images defined in the devspace.yaml, devspace will build the images in parallel. You can still tell devspace to build sequentially with the flag
build-sequential(#533) - Hooks: You are now able to define custom commands that are executed at certain points during the devspace pipeline execution. Currently supported is before / after image building and deploying. In addition it is also possible to execute custom commands directly before or after a certain deployment. See examples for an example. (#535)
- New predefined variables: You are now able to use these predefined variables in your devspace.yaml:
DEVSPACE_RANDOM: A random string, that will be different every time the devspace.yaml is loaded (useful as tag for an image)
DEVSPACE_TIMESTAMP: The current unix timestamp in seconds when the config was loaded by devspace
DEVSPACE_GIT_COMMIT: The current git head short hash (useful as tag for an image)
- New flag
--deploymentsfordevspace deployanddevspace devto only deploy a specific deployment
Changes:
- If the docker daemon cannot be reached but builder is docker, devspace will fallback to building with kaniko instead. If you want devspace to fail instead, you can set the config option images.your_image.build.docker.disableFallback to true.
- New config version v1beta2, you can update your current config with
devspace update config devspace dev,devspace deployanddevspace purgehave an--namespaceflag that let's you redirect devspace to another kubectl namespace
Fixes & Improvements:
- Fixed an issue where the image name was not correctly replaced, if the image has never been built.
- Fixed an issue with internal caching mechanism which sometimes could lead to unnecessary redeploys
- Fixed an issue when you switched spaces the cached hashes where not erased (#527)
devspace initdoesn't write kube context anymoredevspace initnow always asks how you would like to initialize your project