From 669a8fce985164632b41bcac8fef3f52223bac0e Mon Sep 17 00:00:00 2001 From: "Chris St. Pierre" Date: Mon, 10 Nov 2014 10:32:10 -0600 Subject: Options: further command registry fixes This updates the documentation for some of the recent changes to subcommand handling, and ensures that the server core is shut down by bcfg2-info. --- doc/development/option_parsing.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'doc/development') diff --git a/doc/development/option_parsing.txt b/doc/development/option_parsing.txt index 642b9a36c..e14031e1e 100644 --- a/doc/development/option_parsing.txt +++ b/doc/development/option_parsing.txt @@ -179,8 +179,9 @@ The normal implementation pattern is this: collect its options and adds it as a :class:`Bcfg2.Options.Subparser` option group to the main option parser. -#. Register your commands with - :func:`Bcfg2.Options.register_commands`. +#. Register your commands with the + :func:`Bcfg2.Options.CommandRegistry.register_commands` method of + your ``CommandRegistry`` object. #. Add options from the :attr:`Bcfg2.Options.CommandRegistry.command_options` attribute to the option parser. @@ -211,9 +212,7 @@ At a minimum, the :func:`Bcfg2.Options.Subcommand.run` method must be overridden, and a docstring written. .. autoclass:: Subcommand -.. autoclass:: HelpCommand .. autoclass:: CommandRegistry -.. autofunction:: register_commands Actions ------- -- cgit v1.2.3-1-g7c22