ufo 3.5.7 → 4.0.0

data/docs/_docs/ufo-tasks-register.md

@@ -11,9 +11,9 @@ ufo tasks register
 You should see something similiar to this:
 
 ```sh
-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/docs/_docs/upgrade4.md

@@ -0,0 +1,49 @@
+---
+title: Upgrading to Version 4
+---
+
+A major change in ufo from version 3 to 4 is that the ECS service is now created by CloudFormation. If you have an existing ECS service deployed by ufo version 3, when you deploy your app again with ufo version 4, there will be a new additional ECS service created. Here is the recommended upgrade path.
+
+## Upgrade Steps Summary
+
+The upgrade path recommended here should result in zero downtime. It is effectively a blue/green deployment with a DNS switchover.
+
+1. Run `ufo upgrade v3to4`
+2. Check the changed files.
+3. Run `ufo ship SERVICE`.
+4. Confirm your new service is working. `ufo ps` and `ufo apps` is useful.
+5. Switch the DNS to the new service's endpoint.
+6. Confirm everything on the new service works.
+7. Destroy the old ECS service with the ECS console. Do not destroy it with `ufo destroy` as the `ufo destroy` command will destroy the newly created service.
+
+Note, with ufo version 4, load balancers are supported and automatically created for web services. If you want to use the existing load balancer, you can do so by specifying `--elb existing-target-group-arn`.
+
+### ufo upgrade v3to4
+
+It is recommended that you run the `ufo upgrade v3to4` command with the network options specified. Please substitute the command with the vpc id and subnets for your setup.  Example:
+
+    $ ufo upgrade v3to4 --vpc-id vpc-111 --ecs-subnets subnet-111 subnet-222 --elb-subnets subnet-333 subnet-444 --force
+    Upgrading structure of your current project to the new ufo version 4 project structure
+          append  .dockerignore
+          append  .gitignore
+           force  .ufo/params.yml
+        conflict  .ufo/settings.yml
+           force  .ufo/settings.yml
+          create  .ufo/settings/cfn/default.yml
+          create  .ufo/settings/network/default.yml
+    Upgrade complete.
+
+If you run the upgrade command without specified options, then ufo will detect and use the default vpc and subnets, which might not be what you want.  Inspect the files and verify that they are what you desired.
+
+### Verify changed files
+
+File | Changes
+--- | ---
+.ufo/params.yml | The create_service and update_service sections have been removed. The options handed by CloudFormation and can be customized with `.ufo/settings/cfn/default.yml`. If you have used these options for Fargate support, you no longer need to worry about them.  The generated CloudFormation template detects if the task definition uses Fargate and handles it for you.
+.ufo/settings.yml | A network_profile and cfn_profile option have been added with default settings.
+.ufo/settings/cfn/default.yml | Starter cfn settings file.
+.ufo/settings/network/default.yml | This generated file will have the vpc and subnets that you specified above.  You can change them directly in this file to control what network settings ufo uses.
+
+<a id="prev" class="btn btn-basic" href="{% link _docs/stuck-cloudformation.md %}">Back</a>
+<a id="next" class="btn btn-primary" href="{% link _docs/run-in-pieces.md %}">Next Step</a>
+<p class="keyboard-tip">Pro tip: Use the <- and -> arrow keys to move back and forward.</p>

data/docs/_docs/variables.md

@@ -2,18 +2,18 @@
 title: Shared Variables
 ---
 
-Often times, you end up using the set of common variables across your task definitions for a project.  Ufo supports a shared variables concept to help with this.  You specify variables files in the `.ufo/variables` folder and they are made availale to your `.ufo/task_definitions.rb` as well as your `.ufo/templates` files.
+Often, you end up using the set of common variables across your task definitions for a project.  Ufo supports a shared variables concept to support this.  You specify variables files in the `.ufo/variables` folder and they are made available to your `.ufo/task_definitions.rb` as well as your `.ufo/templates` files.
 
 For example, given `variables/base.rb`:
 
 ```
-@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")
 ```
 
-You can now use `@image` in your `.ufo/templates/main.json.erb` without having to explicitly declare them in the `.ufo/task_definitions.rb` file.  Variables are automatically made available to all templates and the `task_definition.rb` file also.
+You can now use `@image` in your `.ufo/templates/main.json.erb` without having to declare them in the `.ufo/task_definitions.rb` file explicitly.  Variables are automatically made available to all templates and the `task_definition.rb` file.
 
 ## Layering
 
@@ -22,7 +22,7 @@ Shared variables also support a concept called layering.  The `variables/base.rb
 `.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")
@@ -51,6 +51,6 @@ When `ufo ship` is ran with `UFO_ENV=development` the `variables/development.rb`
 ])
 ```
 
-<a id="prev" class="btn btn-basic" href="{% link _docs/ufo-env.md %}">Back</a>
+<a id="prev" class="btn btn-basic" href="{% link _docs/params.md %}">Back</a>
 <a id="next" class="btn btn-primary" href="{% link _docs/helpers.md %}">Next Step</a>
 <p class="keyboard-tip">Pro tip: Use the <- and -> arrow keys to move back and forward.</p>

data/docs/_docs/why-cloudformation.md

@@ -0,0 +1,22 @@
+---
+title: Why CloudFormation
+---
+
+Version 3 of ufo was a simpler implementation and did not make use of CloudFormation to create the ECS service. In version 4, ufo uses CloudFormation to create the ECS Service.  This is because ufo became more powerful. Notably, support for Load Balancers was added. With this power, also came added complexity. So the complexity was push onto CloudFormation.  Hence, ECS service is implemented as CloudFormation resource in version 4.
+
+My gut was already telling me that with Load Balancer support, the "orchestration" or sequencing logic in ufo would become annoyingly complex and shifting it to CloudFormation would be worth it. Nevertheless, I took the time with quick experimental branch and added Load Balancer support using the aws-sdk directly without CloudFormation.
+
+The pull request for that code is here [ufo/pull/42](https://github.com/tongueroo/ufo/pull/42). An additional tool was created for the non-CloudFormation approach called [balancer](https://github.com/tongueroo/balancer). Balancer is a standalone tool used to create load balancers consistently with "profile" files.
+
+* [ufo/pull/42](https://github.com/tongueroo/ufo/pull/42) - PR for non-CloudFormation. Closed and not used.
+* [ufo/pull/43](https://github.com/tongueroo/ufo/pull/43) - PR for CloudFormation. Merged and used.
+
+The results of the exercise confirm my gut.  Though the CloudFormation implementation requires more upfront investment, it ultimately pays off.  For example, route53 DNS support was added to ufo easily and quickly.  Sometimes the learning curve of CloudFormation can be a deterrent, so I hope that these thoughts help.
+
+You can check the resources created with CloudFormation by clicking on the stack name of in the CloudFormation console.
+
+<img src="/img/docs/cloudformation-resources.png" class="doc-photo" />
+
+<a id="prev" class="btn btn-basic" href="{% link _docs/faq.md %}">Back</a>
+<a id="next" class="btn btn-primary" href="{% link _docs/customize-cloudformation.md %}">Next Step</a>
+<p class="keyboard-tip">Pro tip: Use the <- and -> arrow keys to move back and forward.</p>

data/docs/_includes/about.html

@@ -9,7 +9,7 @@
             </div>
             <div class="row">
                 <div class="col-lg-4 col-lg-offset-2">
-                    <p>Ufo is a tool that makes building and shipping Docker containers to AWS ECS super easy. At a basic level, ufo builds the docker container image, registers that image to ECS as a task definition, and then deploys that task definition to ECS by updating the service. Ufo provides a <code>ufo ship</code> command that deploys your code to ECS.</p>
+                    <p>Ufo is a tool that makes building and shipping Docker containers to AWS ECS easy. At a basic level, ufo builds the docker container image, registers that image to ECS as a task definition, and then deploys that task definition to ECS by updating the service. Ufo provides a <code>ufo ship</code> command that deploys your code to ECS.</p>
                 </div>
                 <div class="col-lg-4">
                     <p>Ufo was built directly from real life production use cases after seeing the same patterns repeated over and over. Ufo allows you to write the AWS task definition json format file in ERB, an easy templating language.  This allows you to reuse the ufo tool with multiple applications and only put the truly application specific business logic in each app code base.</p>

data/docs/_includes/cfn-customize.md

@@ -0,0 +1,39 @@
+The properties in the file `.ufo/settings/cfn/default.yml` map directly to ufo's CloudFormation resources. It allows you to customize the resources.  The keys get transform to CamelCase keys to work with the CloudFormation template.
+
+### Example of Customization
+
+Let's customize the `AWS::ElasticLoadBalancingV2::TargetGroup` resource created by CloudFormation.  We'll adjust the `deregistration_delay.timeout_seconds` to `8`.  Here's the relevant section of the `.ufo/settings/cfn/default.yml`
+
+```
+target_group:
+...
+  target_group_attributes:
+  - key: deregistration_delay.timeout_seconds
+    value: 8
+```
+
+The value will be injected to the generated CloudFormation template under the corresponding "TargetGroup Properties".  The generated template looks something like this:
+
+```
+TargetGroup:
+  Properties:
+...
+    TargetGroupAttributes:
+    - Key: deregistration_delay.timeout_seconds
+      Value: 8
+...
+```
+
+In this way, you can customize and override any property associated with any resource created the ufo CloudFormation stack.
+
+Here's a list of the resources in the [cfn/stack.yml](https://github.com/tongueroo/ufo/blob/master/lib/cfn/stack.yml) that you can customize:
+
+* Ecs
+* EcsSecurityGroup
+* EcsSecurityGroupRule
+* Elb
+* ElbSecurityGroup
+* Listener
+* TargetGroup
+
+For the most up to date list check out the [cfn/stack.yml](https://github.com/tongueroo/ufo/blob/master/lib/cfn/stack.yml) source code directly.

data/docs/_includes/commands.html

@@ -7,13 +7,13 @@
                     <div class="commands">
 {% highlight sh %}
 ufo ship
-
+ufo ps
+ufo current
+ufo apps
+ufo scale
 ufo docker build
-
 ufo tasks build
-
-ufo scale
-
+ufo rollback
 ufo destroy
 {% endhighlight %}
                     </div>
@@ -22,7 +22,7 @@ ufo destroy
                     <h3>variables/base.rb</h3>
                     <div class="commands">
 {% highlight 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_vars(%Q{

data/docs/_includes/css/ufo.css

@@ -72,6 +72,7 @@ section#main .intro-text .skills {
     /*background-color: green;*/
     margin-top: 40px;
     font-size: 1.2em;
+    color: #9acfe0;
 }
 
 .content-nav ul, .content-nav ol {

data/docs/_includes/example.html

@@ -2,16 +2,16 @@
   <div class="container">
     <div class="row">
       <div class="col-lg-12 text-center">
-        <h2>Example: ufo ship hi-web</h2>
+        <h2>Example: ufo ship demo-web</h2>
         <hr class="star-primary">
       </div>
     </div>
     <div class='row'>
       <div class='col-md-offset-1 col-md-10'>
 {% highlight sh %}
-$ ufo ship hi-web
+$ ufo ship demo-web
 Building docker image with:
-  docker build -t tongueroo/hi:ufo-2017-06-11T19-43-19-bc80e84 -f Dockerfile .
+  docker build -t tongueroo/demo-ufo:ufo-2017-06-11T19-43-19-bc80e84 -f Dockerfile .
 Sending build context to Docker daemon 719.4 kB
 Step 1 : FROM ruby:2.3.3
  ---> 0e1db669d557
@@ -52,26 +52,26 @@ Step 11 : CMD bin/web
  ---> 1689ba53ca03
 Removing intermediate container f56d659a2c9e
 Successfully built 1689ba53ca03
-Docker image tongueroo/hi:ufo-2017-06-11T19-43-19-bc80e84 built.  Took 34s.
-The push refers to a repository [docker.io/tongueroo/hi]
+Docker image tongueroo/demo-ufo:ufo-2017-06-11T19-43-19-bc80e84 built.  Took 34s.
+The push refers to a repository [docker.io/tongueroo/demo-ufo]
 0826214f2b9a: Pushed
 ee30634e4a5d: Pushed
 277ff31e79b4: Layer already exists
 a361a4de05df: Layer already exists
 ufo-2017-06-11T19-43-19-bc80e84: digest: sha256:6381ff8d4413edf0c13926def1d55d0f805d169d686f59cdee3abb960b52eb9a size: 3464
-Pushed tongueroo/hi:ufo-2017-06-11T19-43-19-bc80e84 docker image. Took 10s.
+Pushed tongueroo/demo-ufo:ufo-2017-06-11T19-43-19-bc80e84 docker image. Took 10s.
 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.
-hi-web task definition registered.
-Shipping hi-web...
-hi-web service updated on stag cluster with task hi-web
+demo-web task definition registered.
+Shipping demo-web...
+demo-web service updated on stag cluster with task demo-web
 Software shipped!
 Cleaning up docker images...
-Running: docker rmi tongueroo/hi:ufo-2017-06-11T11-37-00-bc80e84
+Running: docker rmi tongueroo/demo-ufo:ufo-2017-06-11T11-37-00-bc80e84
 $
 {% endhighlight %}
       </div>

data/docs/_includes/reference.md

@@ -1,4 +1,4 @@
-Easy Way to Build and Ship Docker Images to AWS ECS.  The main command is ufo ship. Here's summary of what it does:
+Easy Way to Build and Deploy Docker Images to AWS ECS.  The main command is ufo ship. Here's summary of what it does:
 
 1. Builds a docker image.
 2. Registers the ECS template definition.

data/docs/_includes/subnav.html

@@ -15,21 +15,38 @@
             <ul>
                 <li><a href="{% link _docs/structure.md %}">Structure</a></li>
                 <li><a href="{% link _docs/settings.md %}">Settings</a></li>
+                <li><a href="{% link _docs/settings-network.md %}">Settings Network</a></li>
+                <li><a href="{% link _docs/settings-cfn.md %}">Settings Cfn</a></li>
                 <li><a href="{% link _docs/params.md %}">Params</a></li>
-                <li><a href="{% link _docs/ufo-env.md %}">UFO_ENV</a></li>
                 <li><a href="{% link _docs/variables.md %}">Shared Variables</a></li>
                 <li><a href="{% link _docs/helpers.md %}">Helpers</a></li>
                 <li><a href="{% link _docs/conventions.md %}">Conventions</a></li>
-                <li><a href="{% link _docs/auto-completion.md %}">Auto-Completion</a></li>
+                <li><a href="{% link _docs/fargate.md %}">Fargate</a></li>
+                <li><a href="{% link _docs/ufo-env.md %}">Ufo Env</a></li>
+                <li><a href="{% link _docs/ufo-env-extra.md %}">Ufo Env Extra</a></li>
+                <li><a href="{% link _docs/ufo-current.md %}">Ufo Current</a></li>
+                <li><a href="{% link _docs/load-balancer.md %}">Load Balancer</a></li>
+                <li><a href="{% link _docs/security-groups.md %}">Security Groups</a></li>
+                <li><a href="{% link _docs/ssl-support.md %}">SSL Support</a></li>
+                <li><a href="{% link _docs/route53-support.md %}">Route53 Support</a></li>
+                <li><a href="{% link _docs/faq.md %}">FAQ</a></li>
+            </ul>
+        <li>More
+            <ul>
+                <li><a href="{% link _docs/why-cloudformation.md %}">Why CloudFormation</a></li>
+                <li><a href="{% link _docs/customize-cloudformation.md %}">Customize CloudFormation</a></li>
+                <li><a href="{% link _docs/stuck-cloudformation.md %}">Stuck CloudFormation</a></li>
+                <li><a href="{% link _docs/upgrade4.md %}">Upgrade 4</a></li>
                 <li><a href="{% link _docs/run-in-pieces.md %}">Run In Pieces</a></li>
                 <li><a href="{% link _docs/single-task.md %}">Run Single Task</a></li>
                 <li><a href="{% link _docs/migrations.md %}">Database Migrations</a></li>
                 <li><a href="{% link _docs/automated-cleanup.md %}">Automated Cleanup</a></li>
-                <li><a href="{% link _docs/next-steps.md %}">Next Steps</a></li>
-                <li><a href="{% link _docs/faq.md %}">FAQ</a></li>
+                <li><a href="{% link _docs/auto-completion.md %}">Auto-Completion</a></li>
                 <li><a href="{% link articles.md %}">Articles</a></li>
-                <li><a href="{% link reference.md %}">Reference</a></li>
+                <li><a href="{% link _docs/next-steps.md %}">Next Steps</a></li>
+                <li><a href="{% link reference.md %}">CLI Reference</a></li>
             </ul>
         </li>
+        </li>
     </ul>
 </div>

data/docs/_includes/ufo-ship-options.md

@@ -1,11 +1,12 @@
 {:.ship-options}
 Option  | Description
 ------------- | -------------
+`--cluster`  | This decides what cluster to use.  This can also be set in ufo/settings.yml covered in [Settings]({% link _docs/settings.md %}).  The cli option takes highest precedence.
+`--ecr-keep`  | This integer option determines how many old docker images to keep around.  Ufo will automatically delete and clean up docker images at the end of this process. The default is reasonable large at 30.
+`--elb-eip-ids` | EIP Allocation ids to use for network load balancer.  If specified then `--elb-type` is automatically assumed to be `network`.
+`--elb-type` |  ELB type: application or network. Keep current deployed elb type when not specified.
+`--elb` | Decides to create elb, not create elb or use existing target group.
+`--pretty`  | This boolean option determines ufo generates the task definitions in output in a pretty human readable format.
+`--stop-old-tasks`  | This boolean option determines if ufo will call ecs stop-task on the old tasks after deployment. Sometimes old tasks hang around for a little bit with ECS this forces them along a little quicker. This option forceably kills running tasks, so configuring `deregistration_delay.timeout_seconds` is recommended in the cfn settings instead. Note, it seems like deregistration_delay is currently is respected for Application ELBs but not Network ELBs.
 `--task`  | By convention ufo uses the same name for both the ECS service and task definition. You can override this convention with this option.  The conventions are covered on the [Conventions]({% link _docs/conventions.md %}) page.
-`--target-group`  | The ELB target group to use for the ECS service. This is respected if the ECS service is being created the first time. If the ECS service already exists, this option gets ignored.
-`--target-group-prompt`  | This boolean option allows you to bypass setting the ELB target group if desired.
 `--wait`  | This boolean option determines if ufo blocks and waits until the service has been deployed before continuing.
-`--pretty`  | This boolean option determines ufo generates the task definitions in output in a pretty human readable format.
-`--stop-old-tasks`  | This boolean option determines if ufo will call ecs stop-task on the old tasks after deployment. Sometimes old tasks hang around for a little bit with ECS this forces them along a little quicker.
-`--ecr-keep`  | This integer option determines how many old docker images to keep around.  Ufo will automatically delete and clean up docker images at the end of this process. The default is reasonable large at 30.
-`--cluster`  | This decides what cluster to use.  This can also be set in ufo/settings.yml covered in [Settings]({% link _docs/settings.md %}).  The cli option takes highest precedence.

data/docs/_reference/ufo-apps.md

@@ -0,0 +1,36 @@
+---
+title: ufo apps
+reference: true
+---
+
+## Usage
+
+    ufo apps
+
+## Description
+
+List apps.
+
+This command lists ECS services for an ECS cluster. It includes ECS services that were not created by ufo also.  A `Ufo?` column value of `yes` indicates that the ECS service was created by ufo version 4 and above.  If the service was created with ufo version 3 and below then it will show up as `no`.
+
+## Examples
+
+    $ ufo apps
+    Listing ECS services in the development cluster.
+    +--------------------------------------------------+-----------------+---------+-------------+------+
+    |                   Service Name                   | Task Definition | Running | Launch type | Ufo? |
+    +--------------------------------------------------+-----------------+---------+-------------+------+
+    | development-demo-web-Ecs-7GAUAXH5F56M (demo-web) | demo-web:85     | 2       | FARGATE     | yes  |
+    +--------------------------------------------------+-----------------+---------+-------------+------+
+    $
+
+
+## Options
+
+```
+[--verbose], [--no-verbose]  
+[--mute], [--no-mute]        
+[--noop], [--no-noop]        
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
+```
+

data/docs/_reference/ufo-cancel.md

@@ -0,0 +1,24 @@
+---
+title: ufo cancel
+reference: true
+---
+
+## Usage
+
+    ufo cancel SERVICE
+
+## Description
+
+Cancel creation or update of the ECS service.
+
+
+## Options
+
+```
+[--sure], [--no-sure]        # By pass are you sure prompt.
+[--verbose], [--no-verbose]  
+[--mute], [--no-mute]        
+[--noop], [--no-noop]        
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
+```
+

data/docs/_reference/ufo-completion.md

@@ -41,6 +41,6 @@ Auto-completion example usage:
 [--verbose], [--no-verbose]  
 [--mute], [--no-mute]        
 [--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides ufo/settings.yml.
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
 ```
 

data/docs/_reference/ufo-completion_script.md

@@ -22,6 +22,6 @@ To use, add the following to your `~/.bashrc` or `~/.profile`
 [--verbose], [--no-verbose]  
 [--mute], [--no-mute]        
 [--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides ufo/settings.yml.
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
 ```
 

data/docs/_reference/ufo-current.md

@@ -0,0 +1,93 @@
+---
+title: ufo current
+reference: true
+---
+
+## Usage
+
+    ufo current SERVICE
+
+## Description
+
+Switch the current service. Saves to `.ufo/current`
+
+Sets a current service to remember so you do not have to provide the service name all the time.  This shortens the commands
+
+    ufo ship demo-web # before
+    ufo current --service demo-web
+    ufo ship # after
+
+The state information is written to `.ufo/current`.
+
+## Examples
+
+### summary
+
+    ufo current --service demo-web --env-extra 1
+    ufo current --service demo-web --env-extra 1 --services demo-web demo-worker
+    ufo current --service demo-web --env-extra ''
+    ufo current --service demo-web
+    ufo current --env-extra '1'
+
+### service
+
+To set current service:
+
+    ufo current --service demo-web
+    ufo current --service demo-worker
+    ufo current --service demo-web
+
+To view current service, run `ufo current` without any arguments.
+
+    $ ufo current
+    Current service: demo-web
+
+To remove current service:
+
+    ufo current --service ''
+
+### env-extra
+
+To also set a current `UFO_ENV_EXTRA`.
+
+    ufo current --env-extra 1
+
+The extra env setting will be reflected:
+
+    $ ufo current
+    Current service: demo-web
+    Current env_extra: 1
+
+The `UFO_ENV_EXTRA` variable takes higher precedence than the current setting in the saved file.
+
+To unset:
+
+    ufo current --env-extra ''
+
+### services
+
+The ufo ships command builds one docker image and deploys it to multiple ECS services. You can also have ufo remember what services to use with the current command.
+
+    ufo current --services demo-web demo-worker
+    ufo ships # will depoy to both demo-web and demo-worker
+
+### rm all
+
+To remove all current settings use the `--rm` option.
+
+    ufo current --rm
+
+
+## Options
+
+```
+[--rm], [--no-rm]            # Remove all current settings. Removes `.ufo/current`
+[--service=SERVICE]          # Sets service as a current setting.
+[--services=one two three]   # Sets services as a current setting. This is used for ufo ships.
+[--env-extra=ENV_EXTRA]      # Sets UFO_ENV_EXTRA as a current setting.
+[--verbose], [--no-verbose]  
+[--mute], [--no-mute]        
+[--noop], [--no-noop]        
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
+```
+