0853d48927
Ease spinning up a cluster, where binaries are fetched from arbitrary urls. These could be CircleCI `build-binaries` job artifacts, or presigned S3 urls. Co-authored-by: Tim Gross <tgross@hashicorp.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| disable-windows-updates.ps1 | ||
| fix-tls.ps1 | ||
| install-consul.ps1 | ||
| install-docker.ps1 | ||
| install-nuget.ps1 | ||
| provision.ps1 | ||
| userdata.ps1 | ||
README.md
Windows Packer Build
There are a few boilerplate items in the Powershell scripts, explained below.
The default TLS protocol in the version of .NET that our Powershell cmdlets are built in it 1.0, which means plenty of properly configured HTTP servers will reject requests. The boilerplate snippet below sets this for the current script:
# Force TLS1.2
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
We need to run some of the scripts as an administrator role. The following is a safety check that we're doing so:
$RunningAsAdmin = ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")
if (!$RunningAsAdmin) {
Write-Error "Must be executed in Administrator level shell."
exit 1
}