🛫 Pilot Onboarding Console

Pick what you're trying to do. Each journey collects only the inputs it needs and dispatches the GitHub workflows (pilot-onboarding.yml for Journeys 1–4, upload-gpg-key.yml for keys) — you just don't have to know which mode or flag maps to which intent.

Connection — enter a GitHub token to begin
Your token stays in this tab; it is only used for fetch() calls to api.github.com. Classic PAT with repo + workflow, or fine-grained with Actions, Contents and Secrets read/write.
Working on: no spec yet no new key staged

This run required for Journeys 1–4

Shown in the run title and kept in the run record. One line.

Set up a pilot

Do this once per pilot/environment. Journeys 2 and 3 reuse the spec you produce here.

  • Key sync
  • Spec YAML
  • Validate (preflight)

1 Decryption key only if new / rotated

Skip if the pilot's key already lives in Secrets Manager for this environment. Otherwise paste it here: it's encrypted in your browser (libsodium sealed-box) and staged as GPG_KEY_UPLOAD_PAYLOAD. Choose whether to test it on sample data first (Journey 2 will sync it only after a real decrypt works) or sync immediately.

loading libsodium…

“Test-first” stages only; the next sample run (Journey 2) tests this key and persists it on success. “Sync now” needs the spec in step 2 to know pilot / environment / secret path — fill that in first.

1b SFTP connection only if the source is SFTP

If this pilot's files arrive on an SFTP server instead of S3, enter its credentials here. They are encrypted in your browser (libsodium sealed-box), staged as SFTP_KEY_UPLOAD_PAYLOAD, and upload-sftp-key.yml writes them to Secrets Manager at /<namespace>/<env>/sftp_keys.<pilot_id> (the spec in step 2 names pilot / environment / secret path). Then set source.type to sftp in step 2: runs copy the files to the S3 location first, then carry on as usual.

2 Run spec YAML required

Fill the form (generates YAML live), paste an existing spec, or load one already committed in the repo.

Advanced (pipeline mode, table kind, namespace, ticket)
Where it gets committed

3 Validate, then get it reviewed

Validate sends the YAML inline (preflight_only) — checks shape, mandatory fields and that the S3 source exists; nothing is committed. Open PR commits it to a new branch and opens a pull request — a historical run (Journey 4) only accepts a spec merged into the protected branch.