New Features
- Added a new hook type
wait
that will wait for containers or pods to be running before continuing with the pipeline. This can be useful if you want to ensure a certain pod is running before you continue with the pipeline, like a database. For more information please take a look at the docs. An example configuration could look like this:
...
deployments:
- name: my-database
helm:
componentChart: true
values:
...
hooks:
# This hook will ensure that everytime the deployment
# my-database is deployed DevSpace will wait until
# all pods and containers that match the labelSelector
# app.kubernetes.io/component=my-database are running
- wait:
# DevSpace will wait for all containers that match the label selector below to become running.
# If there are init containers, make sure to set terminatedWithCode as well.
running: true
# This can be needed if there are for example init containers
# that terminate instead of become running.
terminatedWithCode: 0
where:
container:
labelSelector:
app.kubernetes.io/component: my-database
# You could also select just a specific container with
# containerName: database-container
when:
after:
deployments: my-database
...
- Added a new hook type
logs
that can print logs of a selected container. This can be useful to print logs of jobs or print the logs of init containers that would not be printed otherwise duringdevspace dev
. For more information, check out the docs. - Added a new flag
--wait
todevspace logs
that waits for pods to become running before printing the logs - Added a new global flag
--inactivity-timeout
that will exit DevSpace automatically if the user is idle for the given amount of time (#1313)
Fixes
- Fixed an issue where devspace sync on linux would miss files on after recreating a folder multiple times locally (#1296)