I have a patching playbook that works fine if the yum package installation doesn’t require any prompts, as per rpm best practices. Well when I ran my patching playbook to update my OS I discovered that mssql-tools upon rpm post-installation prompts to accept the license terms and get the following prompt:
The license terms for this product can be downloaded from http://go.microsoft.com/fwlink/?LinkId=746949 and found in
/usr/share/doc/mssql-tools/LICENSE.txt . By entering ‘YES’,
you indicate that you accept the license terms.
Do you accept the license terms? (Enter YES or NO)
Well this breaks my play. Has anybody figured out a work around for this type of breakage?
I have a patching playbook that works fine if the yum package installation doesn't require any prompts, as per rpm best
practices. Well when I ran my patching playbook to update my OS I discovered that mssql-tools upon rpm
post-installation prompts to accept the license terms and get the following prompt:
The license terms for this product can be downloaded from http://go.microsoft.com/fwlink/?LinkId=746949 and found in
/usr/share/doc/mssql-tools/LICENSE.txt . By entering 'YES',
you indicate that you accept the license terms.
Do you accept the license terms? (Enter YES or NO)
Well this breaks my play. Has anybody figured out a work around for this type of breakage?
Thanks
This is really not a question related to Ansible, but setting the environment variable ACCEPT_EULA to Y
should to the trick: