Files
inbuxa-migrate/tests
jcoffey-dev 053af21f40
ci / test (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 6m51s
ci / announce (pull_request) Skipped
plan --answers, --stay-on-url and --google-key-from-env
What a program needs to run a migration the guide's way without copying
the guide (the Admin migrations screen, step 1b):

- plan --answers FILE DIR writes the guide's plans from its answers:
  plan.json, preview-plan.json and the setup's directory, and says on
  stdout which files to run and which variables hold the secrets. The
  answers carry no secrets; a file that does is refused. The guide now
  writes its plans through the same code.
- --stay-on-url, on import jmap, export, export-directory and
  import-directory, moves every session URL onto the --url origin, for a
  server reached at an address it doesn't advertise (its own loopback, a
  tunnel). The answers' target takes stayOnUrl and allowInvalidCerts.
- import imap --google-key-from-env reads the service account's key from
  $INBUXA_MIGRATE_GOOGLE_KEY; a plan step names it as the googleKey
  secret. A Google source whose keyFile is empty takes the key as its
  secret.
2026-10-30 17:58:30 -07:00
..
2026-10-30 16:14:45 -07:00
2026-10-30 16:14:45 -07:00
2026-10-30 16:14:45 -07:00
2026-10-30 16:14:45 -07:00
2026-10-30 16:14:45 -07:00
2026-10-30 16:14:45 -07:00
2026-10-30 16:14:45 -07:00
2026-05-29 18:02:15 +02:00
2026-10-30 16:14:45 -07:00