Skip to content

Step and _cmd_and_args parameter - command to be executed : what about 'null means no command to execute' ? #385

@dearith

Description

@dearith

I'm trying to override _cmd_and_args in my <plugin_name>.ini config. file in /etc/metwork.config.d/mfdata/plugins directory.

My plugin contains several steps, and for some reason I don't want to execute some steps in a specific configuration.

Let's assume my plugin's name is foo with 2 steps : s1 and s2.

The config.ini file contains :

[step_s1]
_cmd_and_args={{MFDATA_CURRENT_PLUGIN_DIR}}/s1.py {STANDARD_STEP_ARGUMENTS}
...
[step_s2]
_cmd_and_args={{MFDATA_CURRENT_PLUGIN_DIR}}/s2.py {STANDARD_STEP_ARGUMENTS}
...

Let's assume, in production mode, I don't want to execute step_s1, so in the foo.ini in /etc/metwork.config.d/mfdata/plugins, I'm trying to disable the step_s1 by setting 'null', as mentionned as comment in config.ini file:

# Command (and args) to be executed
# Notes :
# - null means no command to execute
...
[step_s1]
_cmd_and_args=null
...

or

...
[step_s1]
_cmd_and_args=
...

But neither of the solutions works, and I get errors in the logs :

usage: plugin_wrapper [-h] [--cwd] [--empty] [--bash-cmds]
                      [--plugins-base-dir PLUGINS_BASE_DIR] [--ignore-cache]
                      PLUGIN_NAME_OR_PLUGIN_HOME COMMAND_AND_ARGS
plugin_wrapper: error: the following arguments are required: COMMAND_AND_ARGS

Is it a bug, or is there something that i didn't understand ?

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions