Sha256: a3e1d8cbf49778c8de6d3b3b9d088eef82c9739331be82247f8b6c5ff7053d59

Contents?: true

Size: 958 Bytes

Versions: 6

Compression:

Stored size: 958 Bytes

Contents

It is useful to sometimes deploy only the task definition without re-building it.  Say for example, you are debugging the task definition and just want to directly edit the `.ufo/output/hi-web.json` definition. You can accomplish this with the `ufo deploy` command.  The `ufo deploy` command will deploy the task definition in `.ufo/output` unmodified.  Example:

    ufo deploy hi-web

The above command does the following:

1. register the `.ufo/output/hi-web.json` task definition to ECS untouched.
2. deploys it to ECS by updating the service

The `ufo deploy` command does less than the `ufo ship` command.  Typically, people use `ufo ship` over the `ufo deploy` command do everything in one step:

1. build the Docker image
2. register the ECS task definition
3. update the ECS service

The `ufo ships`, `ufo ship`, `ufo deploy` command support the same options. The options are presented here again for convenience:

{% include ufo-ship-options.md %}

Version data entries

6 entries across 6 versions & 1 rubygems

Version Path
ufo-3.3.2 lib/ufo/help/deploy.md
ufo-3.3.1 lib/ufo/help/deploy.md
ufo-3.3.0 lib/ufo/help/deploy.md
ufo-3.2.2 lib/ufo/help/deploy.md
ufo-3.2.1 lib/ufo/help/deploy.md
ufo-3.2.0 lib/ufo/help/deploy.md