Certain homebrew casks hang instead of copying themselves to /Applications about ansible-collection-mac HOT 2 CLOSED

I just realised that the expressvpn install does prompt for the sudo password; I was thus able to get my play to execute by supplying the password on the command-line (-e "ansible_become_password=XXXXX") and then forwarding it to the homebrew_cask module via sudo_password: "{{ ansible_become_password }}". This works, so I guess I should close this issue. But it's not very elegant, because I'm already supplying the sudo password interactively via --ask-become-pass and yet I can't find any way to pass that value to the homebrew_cask module (sudo_password: "{{ what_can_I_use_here }}"). Is this truly an unsolved problem in ansible? (I know that I can also set a variable via a vault, but I don't want to do that either: I just wanted to supply the sudo password once, per invocation, by hand.). Is it possible to pass the --ask-become-pass password to homebrew_cask, either implicitly or explicitly? If not then I guess this issue is moot. Thanks in advance!

from ansible-collection-mac.

In case it's of any use, I realised that if I explicitly set ansible_become_pass (instead of ansible_become_password) then that variable becomes available inside the ansible environment and I no longer need to supply the --ask-become-pass argument: so my script now prompts for the password (using read -rs) once, then supplies it explicitly on the command line. Not great for security, but I'm the only user on this system so good enough I guess. Closing now.

from ansible-collection-mac.