Fabian Kramm

@ethankhall @noizwaves thanks for creating this issue! The correct syntax is to use: ``` vars: MY_ENV_VAR: source: env default: my-default ``` which would be then overridable from the .env file...

We'll also update the documentation for this

@ethankhall variables should be shown separately within the `devspace print` section as these could change or not even be defined (in the case of environment variables), so the `vars` section...

@slazak thanks for creating this issue! The hook was removed in v6, and we recommend to use the `after:deploy` event instead. Would that work for you?

@dhruvbaldawa thanks for the issue! Yes the pipeline functions need more examples and explanations! In general the flags are there to override certain parts of the config, so in `build_images`...

@dhruvbaldawa I see! You could use dependencies for that in your wrapper `devspace.yaml` with the newest beta version we just released: ```yaml version: v2beta1 name: test dependencies: service-a: path: ./service-a/devspace.yaml...

@ddl-risong-na thanks for creating this issue! To have this as generic as possible this would require a helm cleanup job on deletion or we need to implement something in the...

@Quasarman @mykiep does this problem still occur on DevSpace v6?

@Tsopic should be fixed with DevSpace v6

@markphillips100 I believe this should work with the latest DevSpace version. Is it currently still a problem?