Appliance workflow scripts, not core y-cluster features

.env.example

@@ -0,0 +1,35 @@
+# Copy to .env (gitignored) and fill in your values:
+#   cp .env.example .env
+#
+# Sourced from the repo root by the scripts under scripts/. Each
+# script bails with `set GCP_PROJECT in .env` (or similar) if a
+# required value is unset.
+
+# === GCP appliance flow (scripts/appliance-qemu-to-gcp.sh) ===
+
+# GCP project where appliance images, VMs, and the persistent
+# data disk live. The bundled service account
+# (gcp-bootstrap-credentials.sh) must have roles/owner here.
+# Example: my-org-appliance
+GCP_PROJECT=
+
+# Path to the GCP service-account JSON. Created via
+# scripts/gcp-bootstrap-credentials.sh on a machine with
+# gcloud Owner access; copy the JSON to this path on the
+# build machine and chmod 600.
+# Example: ~/.config/y-cluster/gcp-appliance.key.json
+GCP_KEY=
+
+# === Hetzner Object Storage publish (scripts/appliance-publish-hetzner.sh) ===
+
+# Path to a file containing HCLOUD_TOKEN and Hetzner Object
+# Storage credentials. Format documented in the script's header.
+# Example: ~/.config/y-cluster/hetzner.env
+H_S3_ENV_FILE=
+
+# === Hetzner Cloud Packer flow (scripts/e2e-appliance-hetzner.sh) ===
+
+# Same file as H_S3_ENV_FILE when HCLOUD_TOKEN + S3 creds
+# co-locate; separate ENV_FILE var historically.
+# Example: ~/.config/y-cluster/hetzner.env
+ENV_FILE=

.gitignore

@@ -1,2 +1,5 @@
 /kustomize-traverse
 /dist/
+
+# operator-local defaults sourced by the appliance scripts
+.env