Zuplo CLI: Deploy
Use these commands to help your manage your deployed Zuplo projects. They must be run from the root of your Zuplo project. And, they assume that you already have Git setup for the project.
See concrete end-to-end examples of how to use this in your CI/CD job at Custom CI/CD.
Common Use Cases
The following examples assume that you are passing in your --api-key either as
an argument or through the ZUPLO_API_KEY environment variable.
Deploying your Gateway
Code
Code
Polling Timeout
By default, the deploy command will poll the status of the deployment every second for 150 seconds. For most deployments this is enough time for the build and deploy process to complete. However, if you have a large project, this may not be enough time. You can increase the timeout by setting the following environment variables.
POLL_INTERVAL- The interval in seconds between each poll. Default is 1 second.MAX_POLL_RETRIES- The maximum number of retries before the command times out. Default is 150.
Code
Note, that even if the CLI times out, the deployment will continue. You can check the status of the deployment in the Zuplo portal.
Examples
Deploy the current Git branch using the branch name as the environment name
Deploy to a specific environment name instead of using the Git branch name
Deploy to a project in a specific account
Use environment variable for API key
Create a new branch and deploy it as a new environment
Options
--account
The account name
string--environment
The value to use for environment name, instead of the current branch name
string--self-hosted-endpoint
The endpoint of your self-hosted service to deploy to
string--fetch-environments
Fetch the environments for your project from Zuplo. If this is false, then the environment will automatically be detected from the git branch.
booleanDefault: falseGlobal options
The following global options are available for all commands: