Skip to main content
abadge import reads an .env file and creates one server-managed item per variable in the active profile.

​
Usage

​
Flags

​
Behavior

1

Parse the .env file

Standard dotenv syntax. KEY=value per line. Comments (#) and blank lines are skipped.
2

Match existing items by label

The label is the env-var key. Existing items with the same label in the active profile are matched.
3

Apply

For new labels: POST /v1/items (server-managed only). For existing labels: skip without --overwrite, update with --overwrite.
4

Print a summary

Five buckets: created, updated, skipped, refused, failed.

​
Summary buckets

​
Exit codes

skipped and refused are intentional outcomes and do not flip the exit code.

​
Constraints

  • Only server-managed items are written. The active profile must be server_managed.
  • Zero-knowledge items can never be overwritten by import. Delete and re-import, or use abadge item update.
  • Values longer than the standard env-var size limit may be rejected by the platform.

​
Example

The created/updated/skipped buckets always print; refused and failed are appended only when nonzero.