Although your initial post amply demonstrates the problem you ran into, we can surmise that what you're trying to accomplish is more interesting. Can we step back a bit and maybe up to a higher level and explore your actual use case? (I have a feeling the answer is going to involve ansible-vault. You've got me curious.)
On Thursday, March 17, 2022 at 3:21:30 PM UTC-4 Todd Lewis wrote: > "Is usable alongside become keywords" is a description of the "becomes" > attribute. The key point for your case is the red "none" in the "Support" > column, which together means that no amount of "become" shenanigans is > going to affect the behavior of include_vars. > > Interpretation of the "Attributes" table is a bit obscure and error prone > from users' perspectives, IMHO. I believe it's showing a peek under the > covers of how modules are implemented. It appears there's a fairly standard > set of attributes, which are influenced by various keywords, config file > settings, environment variables, and runtime conditions, and these > attributes may influence to various degrees different aspects of modules' > operation. "Become" for example influences include_vars not at all. > > On Thursday, March 17, 2022 at 3:04:29 PM UTC-4 [email protected] > wrote: > >> Also, what does "Is usable alongside become keywords" mean? >> > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/88b3ce33-ec9a-4c70-acdd-42c4caa435a0n%40googlegroups.com.
