In scope: Have a single generalized inventory plugin hook. allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered. implement a prompt plugin that accepts a single {{name}} parameter. support lazily evaluating the "prompt plugin" when fetching config for a node or group.
Out of scope: worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars) making a decision on whether target-lookups are special.
{{noformat}} groups: - name: first_group targets: [ .... ] config: ssh: password: _plugin: prompt message: "Password for group pass
In scope: *Have a single generalized inventory plugin hook. *allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered. *implement a prompt plugin that accepts a single {{name}} parameter. support lazily evaluating the "* Do notprompt plugin" when fetching config until something to {{update_target}} for a node or group target which needs this information.
Out of scope: worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars) making a decision on whether target-lookups are special.
In scope: * Have a single generalized inventory plugin hook. * allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered. * implement a prompt plugin that accepts a single {{name}} parameter.
* Do not prompt until something to {{update_target}} for a target which needs this information.
Out of scope: *worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars) *making a decision on whether target-lookups are special.
In scope: * Have a single generalized inventory plugin hook. * allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered. * implement a prompt plugin that accepts a single {{name}} parameter. * Do not prompt until something to {{update_target}} for a target which needs this information.
Out of scope:
worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars)
making a decision on whether target-lookups are special.
In scope: * Have a single generalized inventory plugin hook. * allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered. * implement a prompt plugin that accepts a single {{name}} parameter.
* Do not prompt until something to {{ Whenupdate_target}} for a is called to update target which needs this information config, that indicates the target is actually being used and should be prompted. Don't prompt for targets that aren't used. Out of scope: * worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars) * making a decision on whether target-lookups are special.
Limit to config only for now. The `prompt` plugin will only return a string. Later _plugin could return other data (hash etc). Hook will be inventory_config_lookup