doctl serverless deploy <directory> [flags]
At any time you can use doctl serverless deploy to upload the contents of a functions project in your file system for
testing in your serverless namespace. The project must be organized in the fashion expected by an App Platform Functions
component. The doctl serverless init command will create a properly organized directory for you to work in.
| Option | Description |
|---|---|
--apihost
|
API host to use |
--auth
|
OpenWhisk auth token to use |
--build-env
|
Path to build-time environment file |
--env
|
Path to runtime environment file |
--exclude
|
Functions and/or packages to exclude |
--help
, -h
|
Help for this command |
--include
|
Functions and/or packages to include |
--incremental
|
Deploy only changes since last deploy
Default: false
|
--insecure
|
Ignore SSL Certificates
Default: false
|
--no-triggers
|
Default: false
|
--remote-build
|
Run builds remotely
Default: false
|
--verbose-build
|
Display build details
Default: false
|
--verbose-zip
|
Display start/end of zipping phase for each function
Default: false
|
--yarn
|
Use yarn instead of npm for node builds
Default: false
|
| Command | Description |
|---|---|
| doctl serverless | Develop, test, and deploy serverless functions |
| Option | Description |
|---|---|
--access-token, -t
|
API V2 access token |
--api-url, -u
|
Override default API endpoint |
--config, -c
|
Specify a custom config file
Default:
|
--context
|
Specify a custom authentication context name |
--interactive
|
Enable interactive behavior. Defaults to true if the terminal supports it (default false)
Default: false
|
--output, -o
|
Desired output format [text|json]
Default: text
|
--trace
|
Show a log of network activity while performing a command
Default: false
|
--verbose, -v
|
Enable verbose output
Default: false
|