What a program needs to run a migration the guide's way, without a second copy of the guide's plan building. It's for the migrations screen in inbuxa Admin, where the server runs this tool.
plan --answers FILE DIR writes the guide's plans from its answers: plan.json, preview-plan.json and the setup's directory. It prints which files to run and which variables hold the secrets. The answers carry no secrets, and 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. It's for a server reached at an address it doesn't advertise, such as its own loopback or 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, and a plan step names it as the googleKey secret.
Tests: 1579 pass locally, clippy is clean, and the live inbuxa tests pass. The new tests cover plan end to end (including a preview it wrote, run as is, and a refused secret), --stay-on-url against two mock hosts, and the Google key from the environment.
What a program needs to run a migration the guide's way, without a second copy of the guide's plan building. It's for the migrations screen in inbuxa Admin, where the server runs this tool.
- **`plan --answers FILE DIR`** writes the guide's plans from its answers: `plan.json`, `preview-plan.json` and the setup's directory. It prints which files to run and which variables hold the secrets. The answers carry no secrets, and 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. It's for a server reached at an address it doesn't advertise, such as its own loopback or 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`, and a plan step names it as the `googleKey` secret.
Tests: 1579 pass locally, clippy is clean, and the live inbuxa tests pass. The new tests cover `plan` end to end (including a preview it wrote, run as is, and a refused secret), `--stay-on-url` against two mock hosts, and the Google key from the environment.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What a program needs to run a migration the guide's way, without a second copy of the guide's plan building. It's for the migrations screen in inbuxa Admin, where the server runs this tool.
plan --answers FILE DIRwrites the guide's plans from its answers:plan.json,preview-plan.jsonand the setup's directory. It prints which files to run and which variables hold the secrets. The answers carry no secrets, and a file that does is refused. The guide now writes its plans through the same code.--stay-on-url, onimport jmap,export,export-directoryandimport-directory, moves every session URL onto the--urlorigin. It's for a server reached at an address it doesn't advertise, such as its own loopback or a tunnel. The answers' target takesstayOnUrlandallowInvalidCerts.import imap --google-key-from-envreads the service account's key from$INBUXA_MIGRATE_GOOGLE_KEY, and a plan step names it as thegoogleKeysecret.Tests: 1579 pass locally, clippy is clean, and the live inbuxa tests pass. The new tests cover
planend to end (including a preview it wrote, run as is, and a refused secret),--stay-on-urlagainst two mock hosts, and the Google key from the environment.