provision.sh is provision-gcp.sh - #57
Merged
Merged
Conversation
The network, the firewall, the static address, the snapshot schedule, the audit log and even the ssh are gcloud. What is not -- the machine itself -- is already in cloud-config.yaml and setup.sh, beside it, and any cloud takes those. So a second provider is a second script next to this one, provision-hetzner.sh, not a --provider flag threaded through every function here; the name says which cloud this one is, and leaves room for the next. The pieces two scripts would share -- the password prompt, the checks on a user name and a domain -- stay where they are until there is a second script to share them with. A seam named for a caller that does not exist yet is a guess about its shape. Renamed outright rather than behind a forwarding stub: the curl URL in the README is a day old, and a stub is a second file to keep for as long as anyone might have saved the first. Also: `--help` under `curl | sh` opened with "sed: can't read sh", because the verbs are printed from the file's own header and a piped script has no file -- $0 is the shell's name. The README's own one-liner produced it. With no file, the verbs are said inline. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nearly all of the script is Google's — the network, firewall, static address,
snapshot schedule, audit log and even the ssh are gcloud. The machine itself is
already in
cloud-config.yamlandsetup.sh, which any cloud takes. So a secondprovider becomes
provision-hetzner.shbeside this one rather than a--providerflag threaded through every function; the name says which cloud this is and
leaves room for the next.
The shared pieces (password prompt, user-name and domain checks) stay put until a
second script exists to share them — a seam named for a caller that does not
exist yet is a guess about its shape.
Renamed outright, no forwarding stub: the README's curl URL is a day old.
Also fixes
--helpundercurl | sh, which opened withsed: can't read shbecause the verbs are printed from the file's own header and a piped script has
no file.
curl -fsSL https://raw.githubusercontent.com/AirConsole/switchboard-ide/master/cloud/provision-gcp.sh \ | sh -s -- create mybox --project my-project🤖 Generated with Claude Code