prisma1 deploy

$ prisma1 deploy

Deploys a service configuration to a Prisma service.

Every time you're changing a file from your service configuration, you need to synchronize these changes with the running Prisma service.

Upon the very first deploy of a service, the command will perform initial data seeding if the seed property in prisma.yml is provided. You can prevent this by passing the --no-seed option.

If no endpoint property is specifed in prisma.yml, the command will prompt you to interactively select a Prisma server as a deployment target for the service. After you selected a Prisma server, the CLI writes the endpoint into prisma.yml as the default for future deploys. To bring up the interactive prompt again, simply remove the endpoint property from prisma.yml manually or pass the --new option.

Usage

prisma1 deploy [flags]

Flags

-d, --dry-run    Perform a dry-run of the deployment
-e, --env-file ENV-FILE    Path to .env file to inject env vars
-f, --force    Accept data loss caused by schema changes
-j, --json    Json Output
-n, --new    Force interactive mode to select the cluster
-p, --project PROJECT    Path to Prisma definition file
--no-generate    Disable implicit client generation
--no-migrate    Disable migrations. Prisma 1.26 and above needed
--no-seed    Disable seed on initial service deploy
--skip-hooks    Disable hooks on deploy

Examples

Deploy service configuration in current directory

prisma1 deploy

Deploy service and interactively select a Prisma server as deployment target:

prisma1 deploy --new

Deploy service with environment variables specified in .env.prod

prisma1 deploy --env-file .env.prod