Right now the saltstack version deployed by script/cmtool.bat is hardcoding version 2019.2.2 as the latest. This was being done because issue saltstack/salt-bootstrap#1394 shows that the developers had broken the "latest" parameter that gets passed to the installation script. It seems that the issue is now just waiting for the OP to confirm that the changes actually fix things.
Once the fix is confirmed, we can then likely revert part of commit 14259e45ef604e27d374f79589e745f25a304238 so that "latest" will always correspond to the most recent version of saltstack. To deal with the unsupported ssl-based protocol issues in powershell on the w7 and w2k3 platforms, we can also consider adding KB3154518 to the list of scripts to install.
Right now the saltstack version deployed by
script/cmtool.bat
is hardcoding version2019.2.2
as the latest. This was being done because issue saltstack/salt-bootstrap#1394 shows that the developers had broken the "latest" parameter that gets passed to the installation script. It seems that the issue is now just waiting for the OP to confirm that the changes actually fix things.Once the fix is confirmed, we can then likely revert part of commit 14259e45ef604e27d374f79589e745f25a304238 so that "latest" will always correspond to the most recent version of saltstack. To deal with the unsupported ssl-based protocol issues in powershell on the w7 and w2k3 platforms, we can also consider adding KB3154518 to the list of scripts to install.