Automatically include file argument (or add documentation) on ConfiguredCommand

ConfiguredCommand does not include the configuration file argument automatically but makes you call addFileArgument on bootstrap.

Failing to call this method your command will complain that you’re passing a file argument and none is expected.

This is not documented anywhere:

It would be a good idea to either:

• automatically accept the file argument (this is what the docs say, btw)

• document that the call to addFileArgument is needed.

[joschi]

@pablo-silverback I would expect people to call the parent’s method if they’re overriding a method, i. e. call super(subparser) if they’re overriding the configure(Subparser) method.

If you don’t call super, you’re basically saying that you’re not interested in inheriting the behavior of the parent class.

[pablo-silverback]

From where else could it get the configuration?

From environment variables, from system properties, from a configuration database or configuration service (think Consul or AWS System Manager Parameter Store and similar services).

Isn’t the purpose of ConfiguredCommand to read a configuration file?

No. The purpose is to provide a Configuration to the command (run() method).