Sha256: 877ff2763ca69f6ed5a1b1dbc0e0be61343122a289083a94cf4522e2d2f936f5
Contents?: true
Size: 1.06 KB
Versions: 13
Compression:
Stored size: 1.06 KB
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
### ufo tasks build
To regenerate a `.ufo/output/hi-web.json` definition:
ufo tasks build
### ufo ship
The `ufo deploy` command does less than the `ufo ship` command. Normally, it is recommended to use `ufo ship` over the `ufo deploy` command to 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
13 entries across 13 versions & 1 rubygems