ufo 4.1.1 → 4.1.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +3 -0
- data/Gemfile.lock +1 -1
- data/docs/_reference/ufo-deploy.md +1 -0
- data/lib/ufo/cli.rb +2 -0
- data/lib/ufo/help/deploy.md +11 -2
- data/lib/ufo/tasks/builder.rb +6 -1
- data/lib/ufo/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 913fc3663c65dc235081311b3ecbb30d8deccda12d48b270a109fa937c32a0cd
|
4
|
+
data.tar.gz: bb4e8be1f00d616aa4a291b990e4d7173a5b50a60660ff408f51c0c02714b87e
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: f1cefafb8a8f89a8897311621cae298349a331904b5072e16227139ae361b1b7626d42d7a1b8f56384ac1063b551fe84a507736ff9fb868eca1ba3d69d5a0b7a
|
7
|
+
data.tar.gz: a6c27db5966e491c1a1e39689331939e16e01bbc789a3c8b2c512bb53b177bdc9e4ac3bdd020559476755bda60f171fd9c99f3e930d7ae87fb429c536bc8513a
|
data/CHANGELOG.md
CHANGED
@@ -3,6 +3,9 @@
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
4
4
|
This project *tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
|
5
5
|
|
6
|
+
## [4.1.2]
|
7
|
+
- add --build option for ufo deploy
|
8
|
+
|
6
9
|
## [4.1.1]
|
7
10
|
- add --no-register ability to ufo deploy command
|
8
11
|
- fixes: hide_time_took, ps_spec
|
data/Gemfile.lock
CHANGED
@@ -54,6 +54,7 @@ The `ufo ships`, `ufo ship`, `ufo deploy` command support the same options. The
|
|
54
54
|
# Default: true
|
55
55
|
[--register], [--no-register] # Register task definition
|
56
56
|
# Default: true
|
57
|
+
[--build], [--no-build] # Build task definition
|
57
58
|
[--verbose], [--no-verbose]
|
58
59
|
[--mute], [--no-mute]
|
59
60
|
[--noop], [--no-noop]
|
data/lib/ufo/cli.rb
CHANGED
@@ -47,9 +47,11 @@ module Ufo
|
|
47
47
|
long_desc Help.text(:deploy)
|
48
48
|
ship_options.call
|
49
49
|
option :register, type: :boolean, desc: "Register task definition", default: true
|
50
|
+
option :build, type: :boolean, desc: "Build task definition", default: false
|
50
51
|
def deploy(service=:current)
|
51
52
|
service = service == :current ? Current.service! : service
|
52
53
|
task_definition = options[:task] || service # convention
|
54
|
+
Tasks::Builder.build(options) if options[:build]
|
53
55
|
Tasks::Register.register(task_definition, options) if options[:register]
|
54
56
|
ship = Ship.new(service, options.merge(task_definition: task_definition))
|
55
57
|
ship.deploy
|
data/lib/ufo/help/deploy.md
CHANGED
@@ -7,13 +7,13 @@ The above command does the following:
|
|
7
7
|
1. register the `.ufo/output/demo-web.json` task definition to ECS untouched.
|
8
8
|
2. deploys it to ECS by updating the service
|
9
9
|
|
10
|
-
|
10
|
+
## ufo tasks build
|
11
11
|
|
12
12
|
To regenerate a `.ufo/output/demo-web.json` definition:
|
13
13
|
|
14
14
|
ufo tasks build
|
15
15
|
|
16
|
-
|
16
|
+
## ufo ship
|
17
17
|
|
18
18
|
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:
|
19
19
|
|
@@ -24,3 +24,12 @@ The `ufo deploy` command does less than the `ufo ship` command. Normally, it is
|
|
24
24
|
The `ufo ships`, `ufo ship`, `ufo deploy` command support the same options. The options are presented here again for convenience:
|
25
25
|
|
26
26
|
{% include ufo-ship-options.md %}
|
27
|
+
|
28
|
+
## Creating mutiple environments in parallel
|
29
|
+
|
30
|
+
If you would like to create multiple enviroments quickly in parallel, the `--no-wait` and `--build` option can help speed up the process. Example:
|
31
|
+
|
32
|
+
ufo ship # at least once
|
33
|
+
for i in {1..3}; do
|
34
|
+
UFO_ENV_EXTRA=$i ufo deploy --no-wait --build
|
35
|
+
done
|
data/lib/ufo/tasks/builder.rb
CHANGED
@@ -5,10 +5,15 @@ module Ufo
|
|
5
5
|
# When handling task definitions in with the ship command and class, we always want to
|
6
6
|
# build and register task definitions. There is little point of running them independently
|
7
7
|
# This method helps us do that.
|
8
|
-
|
8
|
+
build(options)
|
9
9
|
Tasks::Register.register(task_definition, options)
|
10
10
|
end
|
11
11
|
|
12
|
+
# ship: build and registers task definitions together
|
13
|
+
def self.build(options)
|
14
|
+
Tasks::Builder.new(options).build
|
15
|
+
end
|
16
|
+
|
12
17
|
def initialize(options={})
|
13
18
|
@options = options
|
14
19
|
end
|
data/lib/ufo/version.rb
CHANGED