1 Commits (f7c5c466be753d12829e745d0d9a046623072995)

Author	SHA1	Message	Date
Abhijit Menon-Sen	276358c885	Introduce inventory.any_unparsed_is_failed configuration setting (#41171) ... In the process of building up the inventory by parsing each inventory source with each available inventory plugin, there are three kinds of possible errors (listed in order from earliest to latest): 1. One source could not be parsed by a particular plugin. 2. One source could not be parsed by any available plugin. 3. ALL sources could not be parsed by any available plugin. The errors in (1) are a part of normal operation, e.g., the script plugin is expected to fail to parse an ini-format source, and we will ignore that error and try the next plugin. There is currently no way to control this, and no known compelling use-case for a setting to control it. This commit does not make any changes here. We implement "any_unparsed_is_failed" to handle (2) above. If enabled, this requires that every available source be parsed validly by at least one plugin. In an inventory comprising a static hosts file and ec2.py, this setting will cause a fatal error if ec2.py fails (a situation that attracted only a warning earlier). We clarify that the existing "unparsed_is_failed=true" setting causes a fatal error only in (3) above, i.e., if NO inventory source could be parsed. In other words, if there is ANY valid source in the inventory (e.g., an ini-format static file), no combination of errors and the setting will cause a fatal error. If you want to execute your playbooks when your inventory is… (a) complete, use "any_unparsed_is_failed=true". (b) not empty, use "unparsed_is_failed=true". The "unparsed_is_failed" setting should be renamed to "all_unparsed_is_failed", but this commit does not do so. Fixes #40512 Fixes #40996	7 years ago