lono 6.1.11 → 7.0.0

data/lib/lono/finder/blueprint.rb

@@ -0,0 +1,11 @@
+module Lono::Finder
+  class Blueprint < Base
+    def type
+      "blueprint"
+    end
+
+    def detection_path
+      "app/templates"
+    end
+  end
+end

data/lib/lono/finder/blueprint/configset.rb

@@ -0,0 +1,17 @@
+class Lono::Finder::Blueprint
+  class Configset < Lono::Finder::Configset
+    def initialize(options={})
+      super
+      @blueprint_root = options[:blueprint_root] || Lono.blueprint_root
+    end
+
+    def local
+      blueprint + vendor + gems
+    end
+
+    def blueprint
+      roots = path_roots("#{@blueprint_root}/app/#{type.pluralize}")
+      components(roots, "blueprint")
+    end
+  end
+end

data/lib/lono/finder/configset.rb

@@ -0,0 +1,11 @@
+module Lono::Finder
+  class Configset < Base
+    def type
+      "configset"
+    end
+
+    def detection_path
+      "lib/configset.*"
+    end
+  end
+end

data/lib/lono/generate.rb

@@ -0,0 +1,93 @@
+module Lono
+  class Generate < AbstractBase
+    # Use class variable to cache this only runs once across all classes. base.rb, diff.rb, preview.rb
+    @@parameters = nil
+    def all
+      return @@parameters if @@parameters
+
+      ensure_s3_bucket_exist
+      pre_generate
+      generate_templates # generates with some placeholders for build_files IE: file://app/files/my.rb
+      post_generate
+      upload_templates
+
+      @@parameters = param_generator.generate  # Writes the json file in CamelCase keys format
+      check_for_errors
+      @@parameters
+    end
+
+    def pre_generate
+      build_scripts
+    end
+
+    def post_generate
+      return if @options[:noop]
+      return if @options[:source]
+      build_files # builds app/files to output/BLUEPRINT/files
+      post_process_template
+      upload_files
+      upload_scripts
+    end
+
+    def param_generator
+      o = {
+        regenerate: true,
+        allow_not_exists: true,
+      }.merge(@options)
+      o = HashWithIndifferentAccess.new(o)
+      Lono::Param::Generator.new(o)
+    end
+    memoize :param_generator
+
+    def ensure_s3_bucket_exist
+      bucket = Lono::S3::Bucket.new
+      return if bucket.exist?
+      bucket.deploy
+    end
+
+    def build_scripts
+      Lono::Script::Build.new(@options).run
+    end
+
+    def build_files
+      Lono::AppFile::Build.new(@options).run
+    end
+
+    def generate_templates
+      Lono::Template::Generator.new(@options).run
+    end
+
+    def post_process_template
+      Lono::Template::PostProcessor.new(@options).run
+    end
+
+    def upload_templates
+      Lono::Template::Upload.new(@options).run
+    end
+
+    def upload_scripts
+      Lono::Script::Upload.new(@options).run
+    end
+
+    def upload_files
+      Lono::AppFile::Upload.new(@options).upload
+    end
+
+    def check_for_errors
+      errors = check_files
+      unless errors.empty?
+        puts "Please double check the command you ran.  There were some errors."
+        puts "ERROR: #{errors.join("\n")}".color(:red)
+        exit
+      end
+    end
+
+    def check_files
+      errors = []
+      unless File.exist?(template_path)
+        errors << "Template file missing: could not find #{template_path}"
+      end
+      errors
+    end
+  end
+end

data/lib/lono/help/blueprint/new.md

@@ -9,7 +9,6 @@
           create  blueprints/demo
           create  blueprints/demo/demo.gemspec
           create  blueprints/demo/.gitignore
-          create  blueprints/demo/.meta/config.yml
           create  blueprints/demo/CHANGELOG.md
           create  blueprints/demo/Gemfile
           create  blueprints/demo/README.md

data/lib/lono/help/cfn/delete.md

@@ -1,7 +1,7 @@
 ## Examples
 
     $ lono cfn delete ec2
-    Are you sure you want to want to delete the stack? (y/N)
+    Are you sure you want to delete the stack? (y/N)
     y
     Deleted example stack.
     $

data/lib/lono/help/cfn/deploy.md

@@ -1,6 +1,6 @@
 The `cfn deploy` command figures out whether or not it should perform a stack create or update. It delegates to `cfn create` or `cfn update`.  This saves you from thinking about it
 
-# Examples
+## Examples
 
 Provided that you are in a lono project and have a `demo` lono blueprint that contains a `demo` template.  To create a stack you can run:
 
@@ -11,82 +11,11 @@ The above command will generate:
 * template:   output/demo/templates/demo.yml
 * parameters: output/demo/params/development.json
 
-By [convention]({% link _docs/conventions/cli.md %}), the blueprint name is the same as the stack name. In turn, template name is the same as the blueprint name. Lastly, the param name will default to the template name.  Some examples follow to help explain.
 
-## Convention: Stack, Blueprint, Template and Parameter are All the Same
+## Conventions
 
-Let's say you have a blueprint in `blueprints/demo` with a structure the looks something like this:
+By [convention]({% link _docs/conventions/cli.md %}), the blueprint name is the same as the stack name. In turn, template name is the same as the blueprint name. Lastly, the param name will match the stack name unless it's explicitly specified with `--config` or `--param`.
 
-    .
-    ├── blueprints
-    │   └── demo
-    │       └── app
-    │           └── templates
-    │               ├── demo.rb
-    │               └── ec2.rb
-    └── configs
-        └── demo
-            └── params
-                ├── base.txt
-                └── development.txt
+Often you want to create a stack name that is different from the blueprint name. Here’s an example of overriding the blueprint name.
 
-The command:
-
-    lono cfn deploy demo
-
-Will use:
-
-* blueprint: blueprints/demo
-* template: blueprints/demo/app/templates/demo.rb
-* param: configs/demo/params/development.txt
-
-## Stack and Blueprint Do Not Match But Everything Else Does
-
-This is a common case, where the stack name is different from the blueprint name.
-
-    lono cfn deploy my-demo --blueprint demo
-
-The stack will be called my-demo and the blueprint is `demo`.  Since by convention, templates default to the blueprint name we're pretty much set.  Lono will use:
-
-* blueprint: blueprints/demo
-* template: blueprints/demo/app/templates/demo.rb
-* param: configs/demo/params/development.txt
-
-Everything is the same as when the stack name matches the blueprint name.
-
-## Blueprint and Template Name Do Not Match, But Template and Param Name Matches
-
-    lono cfn deploy my-demo --blueprint demo --template ec2
-
-In this case we are using the ec2 template within the demo blueprint.  We'll add another param file `configs/demo/params/ec2.txt`
-
-    └── configs
-        └── demo
-            └── params
-                └── ec2.txt
-
-Lono will use these files:
-
-* blueprint: blueprints/demo
-* template: blueprints/demo/app/templates/ec2.rb
-* param: configs/demo/params/ec2.txt
-
-## Template Name and Param Name Do Not Match
-
-The form with most control is the one with all options explicitly specified.
-
-    lono cfn deploy my-demo --blueprint demo --template ec2 --param large
-
-We'll add another parameter file here: `configs/demo/params/ec2/large.txt`
-
-    └── configs
-        └── demo
-            └── params
-                └── ec2
-                    └── large.txt
-
-Lono will use these files:
-
-* blueprint: blueprints/demo
-* template: blueprints/demo/app/templates/ec2.rb
-* param: configs/demo/params/ec2/large.txt
+    lono cfn deploy my-stack --blueprint demo

data/lib/lono/help/cfn/status.md

@@ -13,7 +13,3 @@ Shows the status of the stack. If the stack is in progress then tail the status
     11:52:35PM UPDATE_COMPLETE_CLEANUP_IN_PROGRESS AWS::CloudFormation::Stack ecs-asg
     11:52:36PM UPDATE_COMPLETE AWS::CloudFormation::Stack ecs-asg
 
-If current name is set.
-
-    lono cfn current --name ecs-asg
-    lono cfn status

data/lib/lono/help/cfn/update.md

@@ -21,7 +21,7 @@ By default, the update command will display a preview of the stack changes befor
 
 ## Conventions: template and param
 
-Lono follows some [coventions](http://lono.cloud/docs/conventions/) that helps keep the commands short.  We'll go through an example to explain:
+Lono follows some [coventions](https://lono.cloud/docs/conventions/) that helps keep the commands short.  We'll go through an example to explain:
 
 Provided that you are in a lono project and have a `demo` lono blueprint that contains a `demo` template.  To update a stack you can run:
 

data/lib/lono/help/code/convert.md

@@ -0,0 +1,51 @@
+## Examples
+
+    lono code convert path/to/file
+    lono code convert http://example.com/url/to/template.yml
+    lono code convert http://example.com/url/to/template.json
+
+## Example with Output
+
+    $ lono code convert https://s3-us-east-2.amazonaws.com/cloudformation-templates-us-east-2/AutoScalingMultiAZWithNotifications.template
+    INFO: The ruby syntax is valid
+    INFO: Translated ruby code below:
+
+    aws_template_format_version "2010-09-09"
+    parameter("VpcId",
+      type: "AWS::EC2::VPC::Id",
+      description: "VpcId of your existing Virtual Private Cloud (VPC)",
+      constraint_description: "must be the VPC Id of an existing Virtual Private Cloud."
+    )
+    ...
+    ...
+    ...
+    resource("InstanceSecurityGroup", "AWS::EC2::SecurityGroup",
+      group_description: "Enable SSH access and HTTP from the load balancer only",
+      security_group_ingress: [
+        {
+          ip_protocol: "tcp",
+          from_port: "22",
+          to_port: "22",
+          cidr_ip: ref("SSHLocation")
+        },
+        {
+          ip_protocol: "tcp",
+          from_port: "80",
+          to_port: "80",
+          source_security_group_id: select(0,get_att("ApplicationLoadBalancer","SecurityGroups"))
+        }
+      ],
+      vpc_id: ref("VpcId")
+    )
+    output("URL",
+      description: "The URL of the website",
+      value: join("",[
+          "http://",
+          get_att("ApplicationLoadBalancer","DNSName")
+        ])
+    )
+
+The `INFO` messages are written to stderr so you can grab the translated template Ruby code by directing it to a file. Example:
+
+    lono code convert https://s3-us-east-2.amazonaws.com/cloudformation-templates-us-east-2/AutoScalingMultiAZWithNotifications.template > autoscaling.rb
+    cat autoscaling.rb

data/lib/lono/help/code/import.md

@@ -0,0 +1,30 @@
+## Examples
+
+    lono code import path/to/file
+    lono code import http://example.com/url/to/template.yml
+    lono code import http://example.com/url/to/template.json
+    lono code import http://example.com/url/to/template.json --blueprint myblueprint
+
+## Example with Output
+
+    $ URL=https://s3.amazonaws.com/cloudformation-templates-us-east-1/EC2InstanceWithSecurityGroupSample.template
+    $ lono code import $URL --blueprint ec2
+    => Creating new blueprint called ec2.
+          create  blueprints/ec2
+          create  blueprints/ec2/ec2.gemspec
+          create  blueprints/ec2/.gitignore
+          create  blueprints/ec2/.meta/config.yml
+          create  blueprints/ec2/CHANGELOG.md
+          create  blueprints/ec2/Gemfile
+          create  blueprints/ec2/README.md
+          create  blueprints/ec2/Rakefile
+          create  blueprints/ec2/seed/configs.rb
+          create  blueprints/ec2/app/templates
+          create  blueprints/ec2/app/templates/ec2.rb
+          create  configs/ec2/params/development.txt
+          create  configs/ec2/params/production.txt
+    ================================================================
+    Congrats  You have successfully imported a lono blueprint.
+
+    More info: https://lono.cloud/docs/core/blueprints
+    $

data/lib/lono/help/configsets.md

@@ -0,0 +1,24 @@
+## Examples
+
+When the `lono configsets` command is passed the blueprint will list the configsets for the blueprint.
+
+    $ lono configsets ec2
+    Configsets used by ec2 blueprint:
+    +-------+----------------------+---------+---------+
+    | Name  |         Path         |  Type   |  From   |
+    +-------+----------------------+---------+---------+
+    | httpd | app/configsets/httpd | project | project |
+    +-------+----------------------+---------+---------+
+    $
+
+When there are no arguments passed to the `lono configsets` command it will list the project configsets.
+
+    $ lono configsets
+    Project configsets:
+    +-------+------------------------+---------+
+    | Name  |          Path          |  Type   |
+    +-------+------------------------+---------+
+    | httpd | app/configsets/httpd   | project |
+    | ruby  | vendor/configsets/ruby | vendor  |
+    +-------+------------------------+---------+
+    $

data/lib/lono/help/generate.md

@@ -2,13 +2,13 @@ Generates CloudFormation template, parameter files, and scripts in lono project
 
 ## Examples
 
-    lono generate
-    lono generate --clean
-    lono g --clean # shortcut
+    lono generate BLUEPRINT
+    lono generate BLUEPRINT --clean
+    lono g BLUEPRINT --clean # shortcut
 
 ## Example Output
 
-    $ lono generate
+    $ lono generate ec2
     Generating CloudFormation templates, parameters, and scripts
     Generating CloudFormation templates:
       output/templates/ec2.yml

data/lib/lono/help/new.md

@@ -18,7 +18,6 @@ By default, `lono new` generates a skeleton project. Use `TEMPLATE` to generate
           create  infra/blueprints/demo
           create  infra/blueprints/demo/demo.gemspec
           create  infra/blueprints/demo/.gitignore
-          create  infra/blueprints/demo/.meta/config.yml
           create  infra/blueprints/demo/Gemfile
           create  infra/blueprints/demo/README.md
           create  infra/blueprints/demo/seed/configs.rb
@@ -54,5 +53,5 @@ By default, `lono new` generates a skeleton project. Use `TEMPLATE` to generate
 
       To list and create additional blueprints refer to https://lono.cloud/docs/core/blueprints
 
-    More info: http://lono.cloud/
+    More info: https://lono.cloud/
     $

data/lib/lono/help/sets/delete.md

@@ -0,0 +1,8 @@
+## Example
+
+    $ lono sets delete my-set
+    Are you sure you want to delete the my-set stack set?
+    Be sure that it emptied of stack instances first.
+    Are you sure? (y/N) y
+    Deleting my-set stack set.
+    $

data/lib/lono/help/sets/deploy.md

@@ -0,0 +1,76 @@
+## Example
+
+    $ lono sets deploy my-set --blueprint demo
+    Generating CloudFormation templates for blueprint demo:
+      output/demo/templates/demo.yml
+    Uploading CloudFormation templates...
+    Uploaded: output/demo/templates/demo.yml to s3://lono-bucket-12di8xz5sy72z/development/output/demo/templates/demo.yml
+    Templates uploaded to s3.
+    Generating parameter files for blueprint demo:
+    Using params for development: configs/demo/params/development.txt
+      output/demo/params/development.json
+    Parameter Diff Preview:
+    Running: colordiff /tmp/lono/params-preview/existing.json /tmp/lono/params-preview/new.json
+    There were no differences.
+    Generating CloudFormation source code diff...
+    Running: colordiff /tmp/existing_stack_set.yml /home/ec2-user/environment/infra/output/demo/templates/demo.yml
+    33c33
+    <         Value: '2019-12-19 22:46:33 +0000'
+    ---
+    >         Value: '2019-12-19 23:08:05 +0000'
+    Parameters passed to cfn.update_stack_set:
+    ---
+    stack_set_name: my-set
+    parameters:
+    - parameter_key: GroupDescription
+      parameter_value: my-group-description-1
+    template_url: https://lono-bucket-12di8xz5sy72z.s3.us-west-2.amazonaws.com/development/output/demo/templates/demo.yml
+    template_body: 'Hidden due to size... View at: output/demo/templates/demo.yml'
+    Are you sure you want to update the my-set stack set?
+    Will deploy to:
+      account: 112233445566
+      regions: ap-northeast-1,ap-northeast-2,us-west-1,us-west-2
+      account: 223344556677
+      regions: ap-northeast-1,ap-northeast-2,us-west-1,us-west-2
+
+    Number of stack instances to be updated: 8
+    Are you sure? (y/N) y
+    Updating my-set stack set
+    Stack Set Operation Status: RUNNING
+    Stack Instance statuses... (takes a while)
+    2019-12-19 11:08:21 PM Stack Instance: account 112233445566 region ap-northeast-1 status OUTDATED reason User initiated operation
+    2019-12-19 11:08:21 PM Stack Instance: account 112233445566 region us-west-2 status OUTDATED reason User initiated operation
+    2019-12-19 11:08:23 PM Stack Instance: account 112233445566 region ap-northeast-2 status OUTDATED reason User initiated operation
+    2019-12-19 11:08:30 PM Stack Instance: account 223344556677 region ap-northeast-1 status OUTDATED reason User initiated operation
+    2019-12-19 11:08:30 PM Stack Instance: account 223344556677 region ap-northeast-2 status OUTDATED reason User initiated operation
+    2019-12-19 11:08:30 PM Stack Instance: account 112233445566 region us-west-1 status OUTDATED reason User initiated operation
+    2019-12-19 11:08:30 PM Stack Instance: account 223344556677 region us-west-1 status OUTDATED reason User Initiated
+    2019-12-19 11:08:31 PM Stack Instance: account 223344556677 region us-west-2 status OUTDATED reason User initiated operation
+    2019-12-19 11:08:49 PM Stack Instance: account 223344556677 region us-west-1 status CURRENT
+    2019-12-19 11:08:58 PM Stack Instance: account 112233445566 region us-west-1 status OUTDATED reason User Initiated
+    2019-12-19 11:09:17 PM Stack Instance: account 112233445566 region us-west-1 status CURRENT
+    2019-12-19 11:09:28 PM Stack Instance: account 112233445566 region ap-northeast-2 status OUTDATED reason User Initiated
+    2019-12-19 11:09:51 PM Stack Instance: account 112233445566 region ap-northeast-2 status CURRENT
+    2019-12-19 11:10:03 PM Stack Instance: account 223344556677 region ap-northeast-2 status OUTDATED reason User Initiated
+    2019-12-19 11:10:27 PM Stack Instance: account 223344556677 region ap-northeast-2 status CURRENT
+    2019-12-19 11:10:36 PM Stack Instance: account 112233445566 region ap-northeast-1 status OUTDATED reason User Initiated
+    2019-12-19 11:10:59 PM Stack Instance: account 112233445566 region ap-northeast-1 status CURRENT
+    2019-12-19 11:11:08 PM Stack Instance: account 223344556677 region ap-northeast-1 status OUTDATED
+    2019-12-19 11:11:13 PM Stack Instance: account 223344556677 region ap-northeast-1 status OUTDATED reason User Initiated
+    2019-12-19 11:11:36 PM Stack Instance: account 223344556677 region ap-northeast-1 status CURRENT
+    2019-12-19 11:11:46 PM Stack Instance: account 112233445566 region us-west-2 status OUTDATED reason User Initiated
+    2019-12-19 11:12:09 PM Stack Instance: account 112233445566 region us-west-2 status CURRENT
+    2019-12-19 11:12:19 PM Stack Instance: account 223344556677 region us-west-2 status OUTDATED reason User Initiated
+    Stack Set Operation Status: SUCCEEDED
+    2019-12-19 11:12:42 PM Stack Instance: account 223344556677 region us-west-2 status CURRENT
+    Time took to complete stack set operation: 4m 29s
+    Stack Set Operation Summary:
+    account 223344556677 region us-west-1 status SUCCEEDED
+    account 112233445566 region us-west-2 status SUCCEEDED
+    account 112233445566 region ap-northeast-1 status SUCCEEDED
+    account 112233445566 region ap-northeast-2 status SUCCEEDED
+    account 223344556677 region ap-northeast-2 status SUCCEEDED
+    account 223344556677 region us-west-2 status SUCCEEDED
+    account 112233445566 region us-west-1 status SUCCEEDED
+    account 223344556677 region ap-northeast-1 status SUCCEEDED
+    demo