Viper automatically reflects SET SQLCMD_ env vars into the sqlconfig file. So when a user SET SQLCMD_EULA, accept_eula is getting persisted into the sqlconfig file. I don't think it is being honored when sqlcmd create is actually run, so it is benign, but it shouldn't be there.
Viper automatically reflects SET SQLCMD_ env vars into the sqlconfig file. So when a user SET SQLCMD_EULA, accept_eula is getting persisted into the sqlconfig file. I don't think it is being honored when
sqlcmd createis actually run, so it is benign, but it shouldn't be there.