Description
After apisix start -c invalid_config.yaml with an invalid config and erroring out, restarting APISIX without any custom config.yaml should not trigger any more errors related to the previous invalid_config.yaml. However, it currently does.
Steps to Reproduce
$ echo 'hahahahaha` > test.yaml
$
$ sudo apisix start -c test.yaml
/usr/local/openresty//luajit/bin/luajit /usr/local/apisix/apisix/cli/apisix.lua start -c test.yaml
Use customized yaml: test.yaml
/usr/local/openresty//luajit/bin/luajit: /usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:707: failed to classify line: hahahahaha
stack traceback:
[C]: in function 'error'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:707: in function 'parsemap'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:793: in function 'parsedocuments'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:818: in function 'parse'
/usr/local/apisix/apisix/cli/file.lua:241: in function 'read_yaml_conf'
/usr/local/apisix/apisix/cli/ops.lua:174: in function 'init'
/usr/local/apisix/apisix/cli/ops.lua:826: in function </usr/local/apisix/apisix/cli/ops.lua:742>
/usr/local/apisix/apisix/cli/ops.lua:959: in function 'execute'
/usr/local/apisix/apisix/cli/apisix.lua:40: in main chunk
[C]: at 0x00405290
$
$ sudo apisix start
/usr/local/openresty//luajit/bin/luajit /usr/local/apisix/apisix/cli/apisix.lua start
/usr/local/openresty//luajit/bin/luajit: /usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:707: failed to classify line: hahahahaha
stack traceback:
[C]: in function 'error'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:707: in function 'parsemap'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:793: in function 'parsedocuments'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:818: in function 'parse'
/usr/local/apisix/apisix/cli/file.lua:241: in function 'read_yaml_conf'
/usr/local/apisix/apisix/cli/ops.lua:174: in function 'init'
/usr/local/apisix/apisix/cli/ops.lua:826: in function </usr/local/apisix/apisix/cli/ops.lua:742>
/usr/local/apisix/apisix/cli/ops.lua:959: in function 'execute'
/usr/local/apisix/apisix/cli/apisix.lua:40: in main chunk
[C]: at 0x00405290
$
$ sudo apisix reload
/usr/local/openresty//luajit/bin/luajit /usr/local/apisix/apisix/cli/apisix.lua reload
/usr/local/openresty//luajit/bin/luajit: /usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:707: failed to classify line: hahahahaha
stack traceback:
[C]: in function 'error'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:707: in function 'parsemap'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:793: in function 'parsedocuments'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:818: in function 'parse'
/usr/local/apisix/apisix/cli/file.lua:241: in function 'read_yaml_conf'
/usr/local/apisix/apisix/cli/ops.lua:174: in function 'init'
/usr/local/apisix/apisix/cli/ops.lua:916: in function </usr/local/apisix/apisix/cli/ops.lua:914>
/usr/local/apisix/apisix/cli/ops.lua:959: in function 'execute'
/usr/local/apisix/apisix/cli/apisix.lua:40: in main chunk
[C]: at 0x00405290
$
$ sudo apisix restart
/usr/local/openresty//luajit/bin/luajit /usr/local/apisix/apisix/cli/apisix.lua restart
/usr/local/openresty//luajit/bin/luajit: /usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:707: failed to classify line: hahahahaha
stack traceback:
[C]: in function 'error'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:707: in function 'parsemap'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:793: in function 'parsedocuments'
/usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:818: in function 'parse'
/usr/local/apisix/apisix/cli/file.lua:241: in function 'read_yaml_conf'
/usr/local/apisix/apisix/cli/ops.lua:174: in function 'init'
/usr/local/apisix/apisix/cli/ops.lua:865: in function 'test'
/usr/local/apisix/apisix/cli/ops.lua:908: in function </usr/local/apisix/apisix/cli/ops.lua:906>
/usr/local/apisix/apisix/cli/ops.lua:959: in function 'execute'
/usr/local/apisix/apisix/cli/apisix.lua:40: in main chunk
[C]: at 0x00405290
Environment
- APISIX version (run
apisix version): 3.2.0
- Installation: RPM installation on CentOS Stream 8
Description
After
apisix start -c invalid_config.yamlwith an invalid config and erroring out, restarting APISIX without any customconfig.yamlshould not trigger any more errors related to the previousinvalid_config.yaml. However, it currently does.Steps to Reproduce
Environment
apisix version): 3.2.0