The previous version of this control-tower fork stopped working as it was trying to download a version of bosh-cli that is no longer accessible, with exec format error being thrown when attempting to read one of the binaries for an external dependency.
After much digging around, we were able to pin the issue to control-tower trying to download a version of bosh-cli that is no longer accessible. The S3 bucket was likely recently deleted/altered. The download path isn't actually specified in the control-tower repo, but in a separate repo called control-tower-ops that you need to download in order to compile a binary locally: https://github.com/EngineerBetter/control-tower-ops/blob/master/createenv-dependencies-and-cli-versions-aws.json#L10
https://s3.amazonaws.com/bosh-cli-artifacts/bosh-cli-7.2.0-linux-amd64 no longer exists, and trying to access it returns the same error as in the binary giving the exec format error error.
This update fixes fix exec format error with a newly recompiled binary, having first updated the bosh-cli source in https://github.com/EngineerBetter/control-tower-ops/blob/master/createenv-dependencies-and-cli-versions-aws.json to the following:
"bosh-cli": {
"windows": "https://github.com/cloudfoundry/bosh-cli/releases/download/v7.2.0/bosh-cli-7.2.0-windows-amd64.exe",
"mac": "https://github.com/cloudfoundry/bosh-cli/releases/download/v7.2.0/bosh-cli-7.2.0-darwin-amd64",
"linux": "https://github.com/cloudfoundry/bosh-cli/releases/download/v7.2.0/bosh-cli-7.2.0-linux-amd64",
"version": "7.2.0"
}
There were also a few hard coded references to the original Engineer-Better repo that we pointed to this fork, as the renew-https-certificate job was trying to download the original version.