adj source create
Register a Postgres source (creds go straight to the data plane)
Register a Postgres (RDS-compatible) source to import golden snapshots from.
Two things happen:
- The endpoint coordinates (host/port/dbname/sslmode) and the NAME of the credentials Secret are registered with the control plane.
- The read-only username/password are written as a Kubernetes Secret directly into your data-plane cluster (namespace adjoint-import) via kubectl. The values never transit or persist in the Adjoint control plane.
Prefer ADJ_SOURCE_PASSWORD over typing the password into flags. With --skip-secret (or if kubectl is unavailable) step 2 is skipped and the command prints how to plant the Secret manually with 'adj import secret-template'.
Usage
adj source create --host <endpoint> --dbname <db> [flags]
Flags
| Flag | Shorthand | Default | Description |
|---|---|---|---|
--creds-secret |
— |
data-plane Secret name for the creds (default: adjoint-src-<dbname>) | |
--dbname |
— |
source database name (required) | |
--host |
— |
source Postgres host (required) | |
--kubeconfig |
— |
kubeconfig for the data-plane cluster (default: ADJ_KUBECONFIG, then the context's adj-owned kubeconfig) | |
--namespace |
adjoint-import |
staging namespace the import runs in | |
--port |
5432 |
source Postgres port | |
--skip-secret |
false |
register metadata only; do not apply the creds Secret | |
--sslmode |
require |
sslmode: disable|require|verify-ca|verify-full | |
--username |
— |
read-only DB username (else prompt) |
Global flags
| Flag | Shorthand | Default | Description |
|---|---|---|---|
--context |
— |
config context to use (overrides current-context) | |
--output |
-o | table |
output format: table|json|yaml |
--server |
— |
server base URL (overrides the active context) | |
--token |
— |
access token (overrides the active context) | |
--verbose |
-v | false |
log requests to stderr |