DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
What happened?
I noticed --no-warn or anything like that doesn't work for devspace run even if the run is just doing a command that is just echo "hello".
What did you expect to happen instead?
I expected there to be a way to ignore warn Are you using the correct namespace? or warn Deploying into the 'default' namespace is usually not a good idea as this namespace cannot be deleted warnings. These warnings didn't pop up until version 6.3.11 of devspace.
How can we reproduce the bug? (as minimally and precisely as possible)
Make sure you have switched namespaces or just point to default then run devspace run test with the below devspace.yaml. You should get a warning about the context, and have no way to ignore that warning. If you lower your version down to 6.3.10 then it should work again.
My devspace.yaml:
version: v2beta1
commands:
test: |-
echo "hello"
Local Environment:
DevSpace Version: 6.3.12
Operating System: mac
ARCH of the OS: i386
Kubernetes Cluster:
Cloud Provider: aws
Kubernetes Version: v1.29.1-eks-b9c9ed7
Anything else we need to know?
I tried this out in other versions and it worked in 6.3.10 or lower so I think the change is in 6.3.11, possibly this change.
What happened?
I noticed
--no-warnor anything like that doesn't work fordevspace runeven if the run is just doing a command that is justecho "hello".What did you expect to happen instead?
I expected there to be a way to ignore
warn Are you using the correct namespace?orwarn Deploying into the 'default' namespace is usually not a good idea as this namespace cannot be deletedwarnings. These warnings didn't pop up until version 6.3.11 of devspace.How can we reproduce the bug? (as minimally and precisely as possible)
Make sure you have switched namespaces or just point to default then run
devspace run testwith the below devspace.yaml. You should get a warning about the context, and have no way to ignore that warning. If you lower your version down to 6.3.10 then it should work again.My devspace.yaml:
Local Environment:
Anything else we need to know?
I tried this out in other versions and it worked in 6.3.10 or lower so I think the change is in 6.3.11, possibly this change.