Hi Shreya,

I am afraid that I am not aware of anything like this.

On Thu, Nov 5, 2020 at 12:21 PM Shreya Bhardwaj <[email protected]>
wrote:

> Any Updates on this please?
>
> Thanks,
> Shreya Bhardwaj
>
> On Tuesday, November 3, 2020 at 12:56:56 PM UTC+5:30 Shreya Bhardwaj wrote:
>
>> Sure.
>>
>> When I run a playbook,  the output I get on the shell  includes something
>> like:
>>
>> "ansible_facts": {
>>         "discovered_interpreter_python": "/usr/bin/python"
>>     },
>>     "changed": false,
>>     "invocation": {
>>         "module_args": {
>>             "capacity": null,
>>             "controller_id": null,
>>               .
>>               so on
>>               .
>>  }
>>     },
>>     "msg": "Successfully completed the view storage volume operation",
>>     "storage_status": {
>>         "Message": {
>>
>> when I register, the output I get is just the "msg" block, whereas I wish
>> to capture the invocation/module_args block
>> The module_args block contains some information that I need to make use
>> of.
>>
>> I hope I was able to explain.
>>
>> On Monday, November 2, 2020 at 1:55:59 PM UTC+5:30 Abhijeet Kasurde wrote:
>>
>>> module_args accepts user input. That means those are already with the
>>> user. I am not sure how that will be useful. Can you provide a use case?
>>>
>>> On Mon, Nov 2, 2020 at 1:46 PM Shreya Bhardwaj <[email protected]>
>>> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> I wanted to capture the data present in the module_args.
>>>> But when I register the output in a variable, I don't get the
>>>> invocation{module_args} part in it.
>>>>
>>>> The way we access ansible facts:  {ansible facts['whatever you want to
>>>> know']['xyz']}
>>>>
>>>> Is there a way to access the module_args in the playbook or use them in
>>>> conditionals somehow?
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> 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/291cc177-8f41-4241-8401-6111b102ef45n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/ansible-project/291cc177-8f41-4241-8401-6111b102ef45n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>>
>>> --
>>> Thanks,
>>> Abhijeet Kasurde
>>>
>> --
> 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/08d9152b-9e88-4c85-9c80-4dd56fe6ebd5n%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/08d9152b-9e88-4c85-9c80-4dd56fe6ebd5n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Thanks,
Abhijeet Kasurde

-- 
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/CAFwWkHqspVe81HS1JXw0Vpx2GB%2Bz-VJasdCq-%2B21BghO%3DetCPw%40mail.gmail.com.

Reply via email to