2 Commits (ec78526b976481f3fcdf91a904eeaa68b89ccdea)

Author	SHA1	Message	Date
snipfoo	5f4e332e37	Fix condition for unquoting configuration strings from ini files (#82388) ... * Add prefix to `origin` when configuration variables come from ini files Fixes ansible#82387 This change was suggested by @bcoca in https://github.com/ansible/ansible/pull/82388#discussion_r1424235728 and https://github.com/ansible/ansible/pull/82388#discussion_r1424249732 When configuration variables come from an ini file, their `origin` is now set to `ini: <file>`. Similarly, once supported, YAML configuration files will have their `origin` as `yaml: <file>`. Consequently, since unquoting configuration strings should happen if and only if they come from an ini file, this condition boils down to testing whether their `origin` starts with `ini:`. * Do not add prefix to `origin` but explicitly pass `origin_ftype` So as not to rely on a specific format of the `origin` string, as suggested by @sivel in https://github.com/ansible/ansible/pull/82388#issuecomment-1881714871	8 months ago
Brian Coca	50b6d28ee1	Config init+ (#74914) ... Can now specify plugin/plugin type for list and dump actions New 'init' action to create usable config sources Co-authored-by: Felix Fontein <felix@fontein.de>	3 years ago