From e27568c3ed9fc4750f5a7855e2391599e345cfaa Mon Sep 17 00:00:00 2001 From: lenseB <118888708+lenseB@users.noreply.github.com> Date: Wed, 18 Jun 2025 14:59:46 +0200 Subject: [PATCH] Update developing_plugins.rst I could not find the `_read_config_file()` in the official ansible repo. the `_read_config_data()` is used in the default inventory-plugins like auto, constructed etc. though. Also I'd propose to explain the difference between `_read_config_file()` and `get_option` and add that they are not mutually exclusive. --- docs/docsite/rst/dev_guide/developing_plugins.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/dev_guide/developing_plugins.rst b/docs/docsite/rst/dev_guide/developing_plugins.rst index d45ac41a397..be6bf8dffc1 100644 --- a/docs/docsite/rst/dev_guide/developing_plugins.rst +++ b/docs/docsite/rst/dev_guide/developing_plugins.rst @@ -80,7 +80,7 @@ Some plugin types handle this differently: * Become, callback, connection and shell plugins are guaranteed to have the engine call ``set_options()``. * Lookup plugins always require you to handle it in the ``run()`` method. -* Inventory plugins are done automatically if you use the ``base _read_config_file()`` method. If not, you must use ``self.get_option()``. +* Inventory plugins are done automatically if you use the ``_read_config_data()`` method. If not, you must use ``self.get_option()``. * Cache plugins do it on load. * Cliconf, httpapi and netconf plugins indirectly piggy back on connection plugins. * Vars plugin settings are populated when first accessed (using the ``self.get_option()`` or ``self.get_options()`` method.