ufo 3.5.7 → 4.0.0

data/lib/ufo/help/network/init.md

@@ -0,0 +1,13 @@
+## Examples
+
+    ufo network init # will use default vpc and subnets
+    ufo network init --vpc-id vpc-123
+    ufo network init --vpc-id vpc-123 --subnets subnet-aaa subnet-bbb
+
+If the `--vpc-id` option is set and the `--subnets` is not, then ufo generates files with all the associated subnets from the specified vpc id.
+
+You can also specify name of the settings file to create with the `--filename` option.  Example.
+
+    ufo network init --vpc-id vpc-123 --filename dev
+
+The above command creates a `.ufo/settings/network/dev.yml` file.  You might want to then update your `.ufo/settings.yml` file and update the `network_profile` config to reference it.

data/lib/ufo/help/ps.md

@@ -0,0 +1,27 @@
+## Examples
+
+    $ ufo ps
+    => Service: demo-web
+       Service name: development-demo-web-Ecs-7GAUAXH5F56M
+       Status: ACTIVE
+       Running count: 2
+       Desired count: 2
+       Launch type: FARGATE
+       Task definition: demo-web:85
+       Elb: develop-Elb-1M74CLRS2G0Z4-686742146.us-east-1.elb.amazonaws.com
+    +----------+------+-------------+----------------+---------+-------+
+    |    Id    | Name |   Release   |    Started     | Status  | Notes |
+    +----------+------+-------------+----------------+---------+-------+
+    | f590ee5e | web  | demo-web:85 | 47 minutes ago | RUNNING |       |
+    | fb60ba9f | web  | demo-web:85 | 45 minutes ago | RUNNING |       |
+    +----------+------+-------------+----------------+---------+-------+
+
+Skip the summary info:
+
+    $ ufo ps --no-summary
+    +----------+------+-------------+----------------+---------+-------+
+    |    Id    | Name |   Release   |    Started     | Status  | Notes |
+    +----------+------+-------------+----------------+---------+-------+
+    | f590ee5e | web  | demo-web:85 | 48 minutes ago | RUNNING |       |
+    | fb60ba9f | web  | demo-web:85 | 45 minutes ago | RUNNING |       |
+    +----------+------+-------------+----------------+---------+-------+

data/lib/ufo/help/releases.md

@@ -0,0 +1,16 @@
+## Example
+
+    $ ufo releases
+    Recent task definitions for this service:
+      demo-web:86
+      demo-web:85
+      demo-web:84
+      demo-web:83
+      demo-web:82
+      demo-web:81
+      demo-web:80
+      demo-web:79
+      demo-web:78
+      demo-web:77
+      demo-web:76
+    $

data/lib/ufo/help/resources.md

@@ -0,0 +1,20 @@
+Displays information about the service.
+
+## Examples
+
+    $ ufo resources demo-web
+    Resources:
+    Ecs - AWS::ECS::Service:
+      arn:aws:ecs:us-east-1:111111111111:service/dev-demo-web-Ecs-KN8OVQ7L2N40
+    EcsSecurityGroupRule - AWS::EC2::SecurityGroupIngress:
+      EcsSecurityGroupRule
+    EcsSecurityGroup - AWS::EC2::SecurityGroup:
+      sg-63c17228
+    Elb - AWS::ElasticLoadBalancingV2::LoadBalancer:
+      arn:aws:elasticloadbalancing:us-east-1:111111111111:loadbalancer/app/dev-hi-Elb-1KEVRDILLSUC9/0b9434b7a9a66fb7
+    ElbSecurityGroup - AWS::EC2::SecurityGroup:
+      sg-11b1025a
+    Listener - AWS::ElasticLoadBalancingV2::Listener:
+      arn:aws:elasticloadbalancing:us-east-1:111111111111:listener/app/dev-hi-Elb-1KEVRDILLSUC9/0b9434b7a9a66fb7/1996f1f252d7ba2e
+    TargetGroup - AWS::ElasticLoadBalancingV2::TargetGroup:
+      arn:aws:elasticloadbalancing:us-east-1:111111111111:targetgroup/dev-h-Targe-1VUFA8577XWT7/7e67276c182fdc87

data/lib/ufo/help/rollback.md

@@ -0,0 +1,35 @@
+## Examples
+
+You only need to specific the task definition version number, though you can specify the name also
+
+    ufo rollback demo-web 1
+    ufo rollback demo-web demo-web:1
+
+To see recent task definitions:
+
+    ufo releases
+
+If you set a current service with `ufo current`, then the commands get shorten:
+
+    ufo rollback demo-web:1
+    ufo rollback 1
+
+Note, task definitions get created by many ways with more than just `ufo ship`. So it the previous version might not be the latest version number minus one.
+
+## Using image name
+
+Another way to specify the version for rollback is with the container definition's image value.  Here's the portion of the ecs task definition that you would look for:
+
+    ...
+    "container_definitions": [
+      {
+        "name": "web",
+        "image": "tongueroo/demo-ufo:ufo-2018-06-21T15-03-52-ac60240",
+        "cpu": 256,
+    ...
+
+You only need to specify enough for a match to be found.  Ufo searches the 30 most recent task definitions. So all of these would work:
+
+    ufo rollback tongueroo/demo-ufo:ufo-2018-06-21T15-03-52-ac60240
+    ufo rollback 2018-06-21T15-03-52
+    ufo rollback ac60240

data/lib/ufo/help/scale.md

@@ -1,6 +1,26 @@
 Ufo provides a command to scale up and down an ECS service quickly. It is a simple wrapper for `aws ecs update-service --service xxx ----desired-count xxx`.  Here's an example of how you use it:
 
-    $ ufo scale hi-web 3
-    Scale hi-web service in stag cluster to 3
+    $ ufo scale 3
+    Scale demo-web service in development cluster to 3
+
+It is useful to use `ufo ps` to check the status.
+
+    $ ufo ps
+    => Service: demo-web
+       Service name: development-demo-web-Ecs-7GAUAXH5F56M
+       Status: ACTIVE
+       Running count: 2
+       Desired count: 3
+       Launch type: FARGATE
+       Task definition: demo-web:85
+       Elb: develop-Elb-1M74CLRS2G0Z4-686742146.us-east-1.elb.amazonaws.com
+    +----------+------+-------------+----------------+--------------+-------+
+    |    Id    | Name |   Release   |    Started     |    Status    | Notes |
+    +----------+------+-------------+----------------+--------------+-------+
+    | 8f95ef9d | web  | demo-web:85 | PENDING        | PROVISIONING |       |
+    | f590ee5e | web  | demo-web:85 | 50 minutes ago | RUNNING      |       |
+    | fb60ba9f | web  | demo-web:85 | 48 minutes ago | RUNNING      |       |
+    +----------+------+-------------+----------------+--------------+-------+
+    $
 
 While scaling via this method is quick and convenient the [ECS Service AutoScaling](http://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-auto-scaling.html) that is built into ECS is a much more powerful way to manage scaling your ECS service.

data/lib/ufo/help/ship.md

@@ -6,15 +6,15 @@ The main command you use when using ufo is: `ufo ship`.  This command:
 
 Basic usage is:
 
-    ufo ship hi-web
+    ufo ship demo-web
 
 The ECS service gets created if the service does not yet exist on the cluster.
 
 ### Conventions
 
-By convention the task and service names match. If you need override to this convention then you can specific the task.  For example if you want to ship to the `hi-web-1` service and use the `hi-web` task, run:
+By convention the task and service names match. If you need override to this convention then you can specific the task.  For example if you want to ship to the `demo-web-1` service and use the `demo-web` task, run:
 
-    ufo ship hi-web-1 --task hi-web
+    ufo ship demo-web-1 --task demo-web
 
 ## Options in Detail
 
@@ -24,15 +24,31 @@ The command has a decent amount of options, you can see the options available wi
 
 As you can see there are plenty of options for `ufo ship`.  Let's demonstrate usage of them in a few examples.
 
-### Load Balancer Target Group
+### Load Balancer
 
-When you are deploying to a service with the word 'web' in it, ufo assumes that this is a web service that uses a load balancer in front of it.  This is also covered a in the [Conventions]({% link _docs/conventions.md %}) page.  The deploy will prompt you for the ELB `--target-group`  if the ECS does not yet exist.  For non-web container the `--target-group` option gets ignored.  The prommpt can be bypassed by specifying a valid `--target-group` option or specifying the `---no-target-group-prompt` option.
+ECS services can be associated with a Load Balancer upon creation. Ufo can automatically create a load balancer.  The options:
 
-    ufo ship hi-web --no-target-group-prompt
+1. Automatically create the ELB.
+2. Provide a target group from an existing ELB.
+3. No ELB is created.
 
-Or if you would like to specify the target-group upfront and not be bother with the prompted later you can use the `--target-group` option.
+Here are examples for each of them:
 
-    ufo ship hi-web --target-group=arn:aws:elasticloadbalancing:us-east-1:12345689:targetgroup/hi-web/12345
+    ufo ship demo-web --elb=true
+
+    # Use existing target group from pre-created ELB:
+    ufo ship demo-web --elb=arn:aws:elasticloadbalancing:us-east-1:123456789:targetgroup/target-name/2378947392743
+
+    # Disable creating elb and prompt:
+    ufo ship demo-web --elb=false
+
+Note, if the docker container's name is web then the `--elb` flag defaults to true automatically.
+
+If you need to create a network load balancer with pre-allocated EIPs, you can use `--elb-eip-ids`, example:
+
+    ufo deploy demo-web --elb-eip-ids eipalloc-a8de9ca1 eipalloc-a8de9ca2
+
+More info available at the [load balancer docs](http://ufoships.com/docs/load-balancer/).
 
 ### Deploying Task Definition without Docker Build
 
@@ -42,27 +58,37 @@ Let's you want skip the docker build phase and only want use ufo to deploy a tas
 
 By default when ufo updates the ECS service with the new task definition it does so asynchronuously. You then normally visit the ECS service console and then refresh until you see that the deployment is completed.  You can also have ufo poll and wait for the deployment to be done with the `--wait` option
 
-    ufo ship hi-web --wait
+    ufo ship demo-web --wait
 
 You should see output similar to this:
 
-    Shipping hi-web...
-    hi-web service updated on cluster with task hi-web
-    Waiting for deployment of task definition hi-web:8 to complete
+    Shipping demo-web...
+    demo-web service updated on cluster with task demo-web
+    Waiting for deployment of task definition demo-web:8 to complete
     ......
     Time waiting for ECS deployment: 31s.
     Software shipped!
 
+### Route 53 DNS Support
+
+Ufo can automatically create a "pretty" route53 record an set it to the created ELB dns name. This is done in by configuring the `.ufo/settings/network/[profile].yml` file. Example:
+
+    dns:
+      name: "{stack_name}.mydomain.com."
+      hosted_zone_name: mydomain.com. # dont forget the trailing period
+
+Refer to [Route53 Support](http://ufoships.com/docs/route53-support/) for more info.
+
 ### Cleaning up Docker Images Automatically
 
 Since ufo builds the Docker image every time there's a deployment you will end up with a long list of docker images.  Ufo automatically cleans up older docker images at the end of the deploy process if you are using AWS ECR.  By default ufo keeps the most recent 30 Docker images. This can be adjust with the `--ecr-keep` option.
 
-    docker ship hi-web --ecr-keep 2
+    docker ship demo-web --ecr-keep 2
 
 You should see something like this:
 
     Cleaning up docker images...
-    Running: docker rmi tongueroo/hi:ufo-2017-06-12T06-46-12-a18aa30
+    Running: docker rmi tongueroo/demo-ufo:ufo-2017-06-12T06-46-12-a18aa30
 
 If you are using DockerHub or another registry, ufo does not automatically clean up images.
 

data/lib/ufo/help/ships.md

@@ -6,7 +6,7 @@ The `ufo ships` command allows you to deploy the *same* Docker image and task de
 
 Instead of using the [ufo ship]({% link _reference/ufo-ship.md %}) and build and deploying the code 3 times you can instead use `ufo ships`.  This will result in the *same* Docker image and *same* task definition being deployed to all 3 services.  Example usage:
 
-    ufo ships hi-web hi-worker hi-clock
+    ufo ships demo-web demo-worker demo-clock
 
 ## Shell expansion
 
@@ -17,14 +17,14 @@ Since the ECS service names are provided as a list you can shorten the command b
 If you're new to shell expansion, run this to understand why above works just as well:
 
     $ echo hi-{web,worker,clock}
-    hi-web hi-worker hi-clock
+    demo-web demo-worker demo-clock
 
 ## Overriding convention
 
 As explained in detail in [Conventions]({% link _docs/conventions.md %}) the task definition and service name are the same by convention.  This convention also applies for each of the services being shipped in the list. The task definition and service names match for each of the services in the list.  If you would like to override the convention as part of the ships command then you use a special syntax. In the special syntax the service and task definition is separated by a colon.  Examples:
 
-    ufo ships hi-web-1:hi-web hi-clock-1 hi-worker-1
-    ufo ships hi-web-1:my-task hi-clock-1:another-task hi-worker-1:third-task
+    ufo ships demo-web-1:demo-web demo-clock-1 demo-worker-1
+    ufo ships demo-web-1:my-task demo-clock-1:another-task demo-worker-1:third-task
 
 ## ufo ships Options
 
@@ -33,12 +33,3 @@ The `ufo ships`, `ufo ship`, `ufo deploy` command support the same options. The
 {% include ufo-ship-options.md %}
 
 Note: The `--task` option is not used with the `ufo ships` command.
-
-## ELB Target Group
-
-For each service being deployed to, ufo will create the ECS service if the service does not yet exist on the cluster.  The deploy process will prompt you for the ELB `--target-group` if you are deploying to a 'web' service that does not yet exist.  Ufo determines that it is a web service by the name of the service. If the service has 'web' in the name then it is considered a web service. If it is not a web service then the `--target-group` option gets ignored.
-
-The prommt can be bypassed by specifying a valid `--target-group` option or specifying the `---no-target-group-prompt` option.  ## Examples
-
-    ufo ships hi-web hi-clock hi-worker --target-group arn:aws:elasticloadbalancing:us-east-1:123456789:targetgroup/hi-web/jsdlfjsdkd
-    ufo ships hi-web hi-clock hi-worker --no-target-group-prompt

data/lib/ufo/help/stop.md

@@ -0,0 +1,7 @@
+ECS deployments can sometimes take a while. One reason could be because the old ECS tasks can take some time to drain and removed. The recommended way to speed this draining process up is configuring the `deregistration_delay.timeout_seconds` to a low value.  You can configured this in `.ufo/settings/cfn/default.yml`. For more info refer to http://localhost:4000/docs/settings-cfn/  This setting works well for Application Load Balancers.
+
+However, for Network Load Balancers, it seems like the deregistration_delay is not currently being respected. In this case, it take an annoying load time and this command can help speed up the process.
+
+The command looks for any extra old ongoing deployments and stops the tasks associated with them.  This can cause errors for any inflight requests.
+
+    ufo stop demo-web

data/lib/ufo/help/task.md

@@ -3,15 +3,15 @@
 You can use the `--command` or `-c` option to override the Docker container command.
 
     ufo task hi-migrate # default command
-    ufo task hi-web --command bin/migrate
-    ufo task hi-web --command bin/with_env bundle exec rake db:migrate:redo VERSION=xxx
-    ufo task hi-web -c uptime
-    ufo task hi-web -c pwd
+    ufo task demo-web --command bin/migrate
+    ufo task demo-web --command bin/with_env bundle exec rake db:migrate:redo VERSION=xxx
+    ufo task demo-web -c uptime
+    ufo task demo-web -c pwd
 
-## Skipping Docker
+## Skipping Docker and Task Registration
 
-The `--no-docker` option is useful. By default, the `ufo task` command will build the docker image.  The docker build process usually is the part that takes the most time. You can skip the docker build process after building it at least once.  This is a faster way to run a bunch of commands with thesame Docker image. Example:
+The `--task-only` option is useful. By default, the `ufo task` command will build the docker image and then register a new task definition.  The docker build process usually is the part that takes the most time. You can skip the docker build process after building it at least once.  This is a faster way to run a bunch of commands with the same Docker image. Example:
 
-  ufo task hi-web -c uptime # build at least once
-  ufo task hi-web --no-docker -c ls # skip docker for speed
-  ufo task hi-web --no-docker -c pwd # skip docker for speed
+  ufo task demo-web -c uptime # build at least once
+  ufo task demo-web --task-only -c ls # skip docker for speed
+  ufo task demo-web --task-only -c pwd # skip docker for speed

data/lib/ufo/help/tasks/build.md

@@ -58,7 +58,7 @@ Here's an example of each of them:
 **task_definitions.rb**:
 
 ```ruby
-task_definition "hi-web" do
+task_definition "demo-web" do
   source "main" # will use ufo/templates/main.json.erb
   variables(
     family: task_definition_name,
@@ -68,7 +68,7 @@ task_definition "hi-web" do
   )
 end
 
-task_definition "hi-worker" do
+task_definition "demo-worker" do
   source "main" # will use ufo/templates/main.json.erb
   variables(
     family: task_definition_name,
@@ -77,7 +77,7 @@ task_definition "hi-worker" do
   )
 end
 
-task_definition "hi-clock" do
+task_definition "demo-clock" do
   source "main" # will use ufo/templates/main.json.erb
   variables(
     family: task_definition_name,
@@ -92,7 +92,7 @@ The shared variables are set in the variables folder:
 **ufo/variables/base.rb**:
 
 ```ruby
-@image = helper.full_image_name # includes the git sha tongueroo/hi:ufo-[sha].
+@image = helper.full_image_name # includes the git sha tongueroo/demo-ufo:ufo-[sha].
 @cpu = 128
 @memory_reservation = 256
 @environment = helper.env_file(".env")
@@ -118,20 +118,20 @@ You should see output similar to below:
     $ ufo tasks build
     Building Task Definitions...
     Generating Task Definitions:
-      ufo/output/hi-web.json
-      ufo/output/hi-worker.json
-      ufo/output/hi-clock.json
+      ufo/output/demo-web.json
+      ufo/output/demo-worker.json
+      ufo/output/demo-clock.json
     Task Definitions built in ufo/output.
     $
 
-Let's take a look at one of the generated files: `.ufo/output/hi-web.json`.
+Let's take a look at one of the generated files: `.ufo/output/demo-web.json`.
 
     {
-      "family": "hi-web",
+      "family": "demo-web",
       "containerDefinitions": [
         {
           "name": "web",
-          "image": "tongueroo/hi:ufo-2017-06-11T22-22-32-a18aa30",
+          "image": "tongueroo/demo-ufo:ufo-2017-06-11T22-22-32-a18aa30",
           "cpu": 128,
           "memoryReservation": 256,
           "portMappings": [

data/lib/ufo/help/tasks/register.md

@@ -4,9 +4,9 @@ The `ufo tasks register` command registers all the generated task definitions in
 
 You should see something similiar to this:
 
-    hi-clock task definition registered.
-    hi-web task definition registered.
-    hi-worker task definition registered.
+    demo-clock task definition registered.
+    demo-web task definition registered.
+    demo-worker task definition registered.
 
 You can verify that the task definitions have been registered properly by viewing the AWS ECS Console Task Definitions page.  You should see something similar to this:
 

data/lib/ufo/help/upgrade/v3to4.md

@@ -0,0 +1,3 @@
+## Examples
+
+    ufo upgrade v3to4 --vpc-id vpc-123 --ecs-subnets subnet-111 subnet-222 --elb-subnets subnet-111 subnet-222

data/lib/ufo/info.rb

@@ -0,0 +1,62 @@
+module Ufo
+  class Info < Base
+    def run
+      unless service
+        puts no_service_message
+        return
+      end
+      puts "Resources:"
+      stack_resources.each do |r|
+        # pp r
+        puts "#{r.logical_resource_id} - #{r.resource_type}:".colorize(:green)
+        puts "  #{r.physical_resource_id}"
+      end
+    end
+
+    # Passing in service so method can be used else where.
+    def load_balancer(service)
+      load_balancer = service.load_balancers.first
+      return unless load_balancer
+
+      resp = elb.describe_target_groups(
+        target_group_arns: [load_balancer.target_group_arn]
+      )
+      target_group = resp.target_groups.first
+      load_balancer_arn = target_group.load_balancer_arns.first # assume first only
+
+      resp = elb.describe_load_balancers(load_balancer_arns: [load_balancer_arn])
+      resp.load_balancers.first
+    end
+    memoize :load_balancer
+
+    def service
+      return unless stack
+
+      service = stack_resources.find { |r| r.resource_type == "AWS::ECS::Service" }
+      arn = service.physical_resource_id
+      resp = ecs.describe_services(services: [arn], cluster: @cluster)
+      resp.services.first
+    end
+    memoize :service
+
+    def stack
+      find_stack(@stack_name)
+    end
+    memoize :stack
+
+    def route53_dns
+      return unless stack
+
+      output = stack.outputs.find do |o|
+        o.output_key == "Route53Dns"
+      end
+      output.output_value if output
+    end
+
+    def stack_resources
+      resp = cloudformation.describe_stack_resources(stack_name: @stack_name)
+      resp.stack_resources
+    end
+    memoize :stack_resources
+  end
+end