Skip to content

ci(deploy): load Cloudflare credentials from the jshvn vault - #7

Merged
jshvn merged 1 commit into
mainfrom
josh/jshvn-vault
Sep 10, 2026
Merged

jshvn merged 1 commit into
mainfrom
josh/jshvn-vault

Conversation

@jshvn

@jshvn jshvn commented Sep 10, 2026

Copy link
Copy Markdown
Owner

What

The two Cloudflare values move from repository secrets into 1Password: vault jshvn, item dispatch, section cloudflare. deploy.yml loads them with load-secrets-action after the test steps, so third-party tooling never has the deploy credentials in its environment, and the one repository secret left is the service account token. README's "Repo secrets" section goes from two secrets to one.

deploy.yml ignores .github/**, so merging this does not deploy; verification is one workflow_dispatch.

Test plan

  • Both references resolve under the new service account, checked by byte count only
  • actionlint clean
  • Real Cloudflare token in the vault item (placeholder today) and OP_SERVICE_ACCOUNT_TOKEN set on this repository before merge
  • One dispatched deploy green after merge
  • Then delete CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID from this repository

The two Cloudflare values move from repository secrets into 1Password, item
dispatch, section cloudflare. The one repository secret left is the service
account token that reads them, loaded after the test steps so third-party
tooling never has the deploy credentials in its environment.
@jshvn
jshvn merged commit 894fc09 into main Sep 10, 2026
1 check passed
@jshvn
jshvn deleted the josh/jshvn-vault branch September 10, 2026 06:09
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.

1 participant