Fabian Kramm

@alexissellier thanks for reporting this issue! We'll investigate this and fix this ASAP if we have found the problem!

@shubhamrajvanshi thanks for reporting this issue! Sounds good to me, we can add that to DevSpace!

Hey @hossko ! Unfortunately WSL2 will require you to move the project onto the linux system or otherwise the file sync cannot work as described here: https://github.com/microsoft/WSL/issues/4739

@emoreth thanks for creating this issue! DevSpace should keep the annotations and labels in the latest beta version, but I agree helm will not delete the replaced deployment automatically if...

@Nafalgar do you need the proxy commands in your case? Seems like the folder `/usr/local/bin` is read only for some reason and cannot be written by DevSpace

@Nafalgar whats the error when you disable those? It should just be erasing the `dev.bot.proxyCommands` option

@tobalsgithub we never call `helm dependency update`, but you could use this snippet to do that in v6: ```yaml pipelines: deploy: |- AWS_PROFILE= helm dependency update run_default_pipeline deploy ```

@tobalsgithub ah yes, you are correct! It seems like you just want to add an environment variable to that command though, which I believe is better done through either pipelines...

@dolfelt not yet, but we will update that very shortly. The following tasks are left todo: 1. Allow string or object as value for vars, pipelines and commands (and all...

@CiiDyR thanks for creating this issue! Your use case makes sense and we'll think about how we can incorporate this into DevSpace