service.yaml
file as below format.Get a new version of YAML by using CLI
new_service.yaml
.Manage the revision
--set-current-active
or -a
to set the new revision as the current active revision and activate the endpoint.API | Status | New CLI API | Description |
---|---|---|---|
vessl serve revision create | Disabled and replaced | vessl serve create | Use with new service.yaml schema. |
vessl serve revision update-autoscaler-config | Disabled and replaced | vessl serve revision scale | Works same but changed in API Signature and options. |
vessl serve gateway <subcommand> | Will be deprecated | N/A | Gateway is automatically managed by the system and other commands. |
vessl serve revision list/show/terminate | Supported | N/A | |
vessl serve create | New | N/A | Uses service.yaml for creating revisions and rolling out them. |
vessl serve create-yaml | New | N/A | Creates service.yaml by project configuration and your inputs. |
vessl serve abort-update | New | N/A | Force stops ongoing rollout and triggers rollback if possible. |
vessl serve update | New | N/A | Updates configuration for traffic splits. |
service-gateway.yaml
file.
Now you can manage gateway configuration by CLI.
vessl serve update
command.