fastly compute deploy

Deploy a package to a Fastly Compute@Edge service.

Syntax

$ fastly compute deploy

Options

Key	Required?	Description
`--service-id`	No	Service ID (falls back to FASTLY_SERVICE_ID, then fastly.toml)
`--service-name`	No	The name of the service
`--version`	No	'latest', 'active', or the number of a specific version
`--comment`	No	Human-readable comment
`--domain`	No	The name of the domain associated to the package
`--name`	No	Package name
`--package`	No	Path to a package tar.gz

Global options

Key	Required?	Description
`--help`	No	Show context-sensitive help.
`--accept-defaults`	No	Accept default options for all interactive prompts apart from Yes/No confirmations
`--auto-yes`	No	Answer yes automatically to all Yes/No confirmations. This may suppress security warnings
`--non-interactive`	No	Do not prompt for user input - suitable for CI processes. Equivalent to --accept-defaults and --auto-yes
`--profile`	No	Switch account profile for single command execution (see also: 'fastly profile switch')
`--token`	No	Fastly API token (or via FASTLY_API_TOKEN)
`--verbose`	No	Verbose logging

Examples

Deploy a package to a Fastly Compute@Edge service

The optional --accept-defaults flag accepts default values for all prompts if configured via the fastly.toml [setup] section and performs a deploy non-interactively

$ fastly compute deploy --accept-defaults

Deploy a custom package to a Fastly Compute@Edge service

Use the fastly compute pack command to package up a pre-compiled Wasm binary and then reference the generated archive file when deploying.

$ fastly compute deploy --package ./pkg/example.tar.gz

API equivalent

This command internally uses the following Fastly public APIs: