What happened:
crictl --config /tmp/crictl.yaml config --set debug=true fails if the file does not exist yet, even though the config command is supposed to bootstrap it.
What you expected to happen:
The command should create the file and write the requested setting.
How to reproduce it (as minimally and precisely as possible):
tmpdir=$(mktemp -d)
crictl --config "$tmpdir/crictl.yaml" config --set debug=true
Current result is a get server config error before the config command runs.
Anything else we need to know?:
This is a normal local CLI workflow. No special scale or boundary conditions are needed.
Environment:
Any host where crictl is run with a custom config path that does not exist yet.
What happened:
crictl --config /tmp/crictl.yaml config --set debug=truefails if the file does not exist yet, even though theconfigcommand is supposed to bootstrap it.What you expected to happen:
The command should create the file and write the requested setting.
How to reproduce it (as minimally and precisely as possible):
Current result is a
get server configerror before theconfigcommand runs.Anything else we need to know?:
This is a normal local CLI workflow. No special scale or boundary conditions are needed.
Environment:
Any host where
crictlis run with a custom config path that does not exist yet.