settings.yml in ufo-3.0.0

- old
+ new
@@ -1,25 +1,27 @@
 # More info: http://ufoships.com/docs/ufo-settings/
-#
-# image:
-# clean_keep: 30
-# ecr_keep: 30
+# The base config is specially treated. It gets included the other environments automatically.
+# Yaml also directly supports merging with & and <<* syntax but doing it automatically
+# for a cleaner syntax.
+base:
+  # image:
+  # clean_keep: 30
+  # ecr_keep: 30
+  # defaults when an new ECS service is created by ufo ship
+  new_service:
+    maximum_percent: 200
+    minimum_healthy_percent: 100
+    desired_count: 1
 
-# aws_profile_ufo_env_map:
-#   default: prod
-#   # More examples:
-#   aws_profile1: prod
-#   aws_profile2: stag
-#   aws_profile3: dev
+development:
+  # cluster: dev
+  # When you have AWS_PROFILE set to one of these values, ufo will switch to the desired
+  # environment. This prevents you from switching AWS_PROFILE, forgetting to
+  # also switch UFO_ENV, and accidentally deploying to production vs development.
+  # aws_profiles:
+  #   - dev_profile1
+  #   - dev_profile2
 
-# ufo_env_cluster_map:
-#   default: prod
-#   # More examples:
-#   aws_profile1: prod
-#   aws_profile2: stag
-#   aws_profile3: dev
-
-# defaults when an new ECS service is created by ufo ship
-new_service:
-  maximum_percent: 200
-  minimum_healthy_percent: 100
-  desired_count: 1
+production:
+  # cluster: prod
+  # aws_profiles:
+  #   - prod_profile