mssql-tools breaks yum update

Archives Ansible Project
1

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

2

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:

- yum:
  ...
  environment:
    ACCEPT_EULA:Y

Reference:
https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-ver15#redhat17

You can also use FreeTDS instead of the Microsoft driver.

Regards
        Racke