Skip to content

Parameterize deploy.sh account (GCP_ACCOUNT) - #11

Merged
amrtgaber merged 1 commit into
mainfrom
chore/parameterize-deploy-account
Jun 16, 2026
Merged

Parameterize deploy.sh account (GCP_ACCOUNT)#11
amrtgaber merged 1 commit into
mainfrom
chore/parameterize-deploy-account

Conversation

@amrtgaber

Copy link
Copy Markdown
Contributor

Removes the hardcoded deployer email from scripts/deploy.sh (it baked a personal address into public git history and failed closed for any other deployer).

The account now comes from a required GCP_ACCOUNT env var, with a clear error if unset:

GCP_ACCOUNT=you@example.com ./scripts/deploy.sh

Deliberately does not fall back to the active gcloud account (avoids deploying as the wrong identity — matches our gcloud hygiene rule).

Closes #8

Removes the hardcoded deployer email from scripts/deploy.sh. The account now
comes from a required GCP_ACCOUNT env var (clear error if unset); we don't fall
back to the active gcloud account, to avoid deploying as the wrong identity.
@amrtgaber
amrtgaber merged commit bb8d6af into main Jun 16, 2026
2 checks passed
@amrtgaber
amrtgaber deleted the chore/parameterize-deploy-account branch June 16, 2026 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parameterize deploy.sh ACCOUNT instead of hardcoding deployer email

1 participant