lono 7.4.11 → 8.0.0.pre.rc1

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

@@ -1,49 +0,0 @@
-## Examples
-
-Let's say we make a simple change to a template, like changing the default InstanceType from `t2.small` to `t2.micro`.  Here's what happens when you run `lono cfn update`
-
-    lono cfn update ec2
-
-The output should look similiar to this:
-
-<img src="/img/tutorials/ec2/cfn-update-instance-type.png" alt="Stack Update" class="doc-photo">
-
-Notice that before the update gets performed lono provides a preview of the changes that are about to take place. There are two types of "diffs" in the preview.
-
-1. Source code diff of the templates. This is generated by downloading the current CloudFormation template and comparing it with the locally generated one using `colordiff`.
-2. CloudFormation Change Set list of changes. This is generated using [AWS CloudFormation Change Set](https://medium.com/boltops/a-simple-introduction-to-cloudformation-part-4-change-sets-dry-run-mode-c14e41dfeab7) feature.
-
-You are prompted with an "Are you sure?" confirmation before lono continues.
-
-By default, the update command will display a preview of the stack changes before applying the update and prompt to check if you are sure.  If you want to bypass the are you sure prompt, use the `--sure` option.
-
-    lono cfn update ec2 --sure
-
-## Conventions: template and param
-
-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:
-
-    lono cfn update demo
-
-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.
-
-Here are examples of overriding the template and params name conventions.
-
-    lono cfn update demo --template different1
-
-The template used is `app/templates/different1.rb` and the parameters used is `configs/demo/params/development/demo/different1.txt`.
-
-    lono cfn update demo --param different2
-
-The template used is `app/templates/demo.rb` and the parameters used is `configs/demo/params/development/demo/different2.json`.
-
-    lono cfn update demo --template different3 --param different4
-
-The template used is `app/templates/different3.rb` and the parameters used is `configs/demo/params/different3/different4.json`.

data/lib/lono/help/cfn.md

@@ -1,7 +0,0 @@
-## Examples
-
-  lono cfn deploy demo
-  lono cfn create demo
-  lono cfn preview demo
-  lono cfn update demo
-  lono cfn delete demo

data/lib/lono/help/new.md

@@ -1,57 +0,0 @@
-## Examples
-
-    lono new infra # starter project with demo blueprint
-
-By default, `lono new` generates a skeleton project. Use `TEMPLATE` to generate different starter projects. List of the [starter templates](https://github.com/tongueroo/lono/tree/master/lib/starter_projects).
-
-## Example Output
-
-    $ lono new infra
-    => Creating new project called infra.
-          create  infra
-          create  infra/.gitignore
-          create  infra/Gemfile
-          create  infra/Guardfile
-          create  infra/README.md
-          create  infra/configs/settings.yml
-    => Creating new blueprint called demo.
-          create  infra/blueprints/demo
-          create  infra/blueprints/demo/demo.gemspec
-          create  infra/blueprints/demo/.gitignore
-          create  infra/blueprints/demo/Gemfile
-          create  infra/blueprints/demo/README.md
-          create  infra/blueprints/demo/seed/configs.rb
-           exist  infra/blueprints/demo
-          create  infra/blueprints/demo/app/templates/demo.rb
-          create  infra/blueprints/demo/app/user_data/bootstrap.sh
-           exist  infra/blueprints/demo/app/templates
-           exist  infra
-          create  infra/configs/demo/params/base.txt
-          create  infra/configs/demo/params/development.txt
-          create  infra/configs/demo/variables/base.rb
-          create  infra/configs/demo/variables/development.rb
-    => Initialize git repo
-    => Installing dependencies with: bundle install
-    => Commit git repo
-    ================================================================
-    Congrats  You have successfully created a lono project.  A starter demo blueprint was created
-    and is at blueprints/demo.  Check things out by going into the created infra folder.
-
-      cd infra
-
-      To create a new blueprint run:
-
-          lono blueprint new demo
-
-      To deploy the blueprint:
-
-          lono cfn deploy my-demo --blueprint demo
-
-      If you name the stack according to conventions, you can simply run:
-
-          lono cfn deploy demo
-
-      To list and create additional blueprints refer to https://lono.cloud/docs/core/blueprints
-
-    More info: https://lono.cloud/
-    $

data/lib/lono/help/param.md

@@ -1,6 +0,0 @@
-## Examples
-
-    $ lono param generate ecs-asg
-    Generating parameter files for blueprint ecs-asg:
-      output/ecs-asg/params/development.json
-    $

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

@@ -1,8 +0,0 @@
-## 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

@@ -1,76 +0,0 @@
-## 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

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

@@ -1,21 +0,0 @@
-## Example
-
-    $ lono sets instances delete my-set --accounts 112233445566 --regions us-west-1 us-west-2
-    Are you sure you want to delete the my-set instances?
-    These stack instances will be deleted:
-
-        accounts: 112233445566
-        regions: us-west-1,us-west-2
-
-
-    Are you sure? (y/N) y
-    Stack Instance statuses... (takes a while)
-    Stack Instance: account 112233445566 region us-west-1 status CURRENT
-    Stack Instance: account 112233445566 region us-west-2 status CURRENT
-    Stack Instance: account 112233445566 region us-west-2 status OUTDATED reason User initiated operation
-    Stack Instance: account 112233445566 region us-west-1 status OUTDATED reason User initiated operation
-    Stack Instance: account 112233445566 region us-west-1 status DELETED
-    Stack Instance: account 112233445566 region us-west-2 status DELETED
-    Time took to complete stack set operation: 30s
-    Stack set operation completed.
-    $

data/lib/lono/help/sets/instances/list.md

@@ -1,14 +0,0 @@
-## Example
-
-    $ lono sets instances list my-set
-    Stack Instance: account 112233445566 region ap-northeast-1 status CURRENT
-    Stack Instance: account 223344556677 region us-west-1 status CURRENT
-    Stack Instance: account 223344556677 region ap-northeast-1 status CURRENT
-    Stack Instance: account 223344556677 region us-west-2 status CURRENT
-    Stack Instance: account 223344556677 region ap-northeast-2 status CURRENT
-    Stack Instance: account 112233445566 region ap-northeast-2 status CURRENT
-    Stack Instance: account 112233445566 region us-west-2 status CURRENT
-    Stack Instance: account 112233445566 region us-west-1 status CURRENT
-    Time took to complete stack set operation: 4m 29s
-    Stack set operation completed.
-    $

data/lib/lono/help/sets/instances/status.md

@@ -1,15 +0,0 @@
-## Example
-
-    $ lono sets instances status my-set
-    Stack Instance statuses... (takes a while)
-    Stack Instance: account 112233445566 region ap-northeast-1 status CURRENT
-    Stack Instance: account 112233445566 region us-west-1 status CURRENT
-    Stack Instance: account 112233445566 region us-west-2 status CURRENT
-    Stack Instance: account 112233445566 region ap-northeast-2 status CURRENT
-    Stack Instance: account 223344556677 region us-west-2 status CURRENT
-    Stack Instance: account 223344556677 region ap-northeast-2 status CURRENT
-    Stack Instance: account 223344556677 region us-west-1 status CURRENT
-    Stack Instance: account 223344556677 region ap-northeast-1 status CURRENT
-    Time took to complete stack set operation: 4m 29s
-    Stack set operation completed.
-    $

data/lib/lono/help/sets/instances/sync.md

@@ -1,90 +0,0 @@
-Lono uses the `config/accounts` and `config/regions` to calculate whether `create-stack-set` or `delete-stack-set` need to be called and calls them accordingly.  You use this instead of `lono sets deploy` when only configs have been adjust and you want to keep the existing template.
-
-Provided:
-
-configs/demo/accounts/development/my-set.txt
-
-    112233445566
-    223344556677
-
-configs/demo/regions/development/my-set.txt
-
-    us-east-1
-    us-east-2
-    us-west-1
-    us-west-2
-
-And then we update:
-
-configs/demo/regions/development/my-set.txt
-
-    us-west-1
-    us-west-2
-    ap-northeast-1
-    ap-northeast-2
-
-Running `lono sets instances sync` will delete and add the stack instances accordingly.
-
-    $ lono sets instances sync my-set --blueprint demo
-    Using regions for development: configs/demo/regions/development/my-set.sh
-    Using accounts for development: configs/demo/accounts/development/my-set.sh
-    Are you sure you want to sync stack instances?
-    lono will run:
-    create_stack_instances for:
-      accounts: 112233445566,223344556677
-      regions: ap-northeast-1,ap-northeast-2
-
-    Number of stack instances to be created: 4
-    delete_stack_instances for:
-      accounts: 112233445566,223344556677
-      regions: us-east-1,us-east-2
-
-    Number of stack instances to be deleted: 4
-
-    Are you sure? (y/N) y
-    => Running create_stack_instances on:
-      accounts: 112233445566,223344556677
-      regions: ap-northeast-1,ap-northeast-2
-    Stack Instance statuses... (takes a while)
-    2019-12-19 10:59:07 PM Stack Instance: account 112233445566 region ap-northeast-1 status OUTDATED reason User initiated operation
-    2019-12-19 10:59:07 PM Stack Instance: account 223344556677 region ap-northeast-1 status OUTDATED reason User initiated operation
-    2019-12-19 10:59:07 PM Stack Instance: account 223344556677 region ap-northeast-2 status OUTDATED reason User initiated operation
-    2019-12-19 10:59:07 PM Stack Instance: account 112233445566 region ap-northeast-2 status OUTDATED reason User initiated operation
-    2019-12-19 10:59:17 PM Stack Instance: account 112233445566 region ap-northeast-1 status OUTDATED reason User Initiated
-    2019-12-19 10:59:26 PM Stack Instance: account 112233445566 region ap-northeast-1 status CURRENT
-    2019-12-19 10:59:40 PM Stack Instance: account 223344556677 region ap-northeast-1 status OUTDATED reason User Initiated
-    2019-12-19 10:59:49 PM Stack Instance: account 223344556677 region ap-northeast-1 status CURRENT
-    2019-12-19 11:00:04 PM Stack Instance: account 112233445566 region ap-northeast-2 status OUTDATED reason User Initiated
-    2019-12-19 11:00:17 PM Stack Instance: account 112233445566 region ap-northeast-2 status CURRENT
-    2019-12-19 11:00:27 PM Stack Instance: account 223344556677 region ap-northeast-2 status OUTDATED reason User Initiated
-    Time took to complete stack set operation: 1m 40s
-    Stack set operation completed.
-    Stack Set Operation Summary:
-    account 112233445566 region ap-northeast-2 status SUCCEEDED
-    account 112233445566 region ap-northeast-1 status SUCCEEDED
-    account 223344556677 region ap-northeast-2 status SUCCEEDED
-    account 223344556677 region ap-northeast-1 status SUCCEEDED
-    => Running delete_stack_instances on:
-      accounts: 112233445566,223344556677
-      regions: us-east-1,us-east-2
-    Stack Instance statuses... (takes a while)
-    2019-12-19 11:00:40 PM Stack Instance: account 112233445566 region us-east-2 status CURRENT
-    2019-12-19 11:00:40 PM Stack Instance: account 112233445566 region us-east-1 status CURRENT
-    2019-12-19 11:00:40 PM Stack Instance: account 223344556677 region us-east-2 status CURRENT
-    2019-12-19 11:00:40 PM Stack Instance: account 223344556677 region us-east-1 status CURRENT
-    2019-12-19 11:00:40 PM Stack Instance: account 223344556677 region us-east-1 status OUTDATED reason User initiated operation
-    2019-12-19 11:00:41 PM Stack Instance: account 223344556677 region ap-northeast-2 status CURRENT
-    2019-12-19 11:00:44 PM Stack Instance: account 112233445566 region us-east-2 status OUTDATED reason User initiated operation
-    2019-12-19 11:00:45 PM Stack Instance: account 112233445566 region us-east-1 status OUTDATED reason User initiated operation
-    2019-12-19 11:00:45 PM Stack Instance: account 223344556677 region us-east-2 status OUTDATED reason User initiated operation
-    2019-12-19 11:01:03 PM Stack Instance: account 112233445566 region us-east-1 status DELETED
-    2019-12-19 11:01:17 PM Stack Instance: account 223344556677 region us-east-1 status DELETED
-    2019-12-19 11:01:31 PM Stack Instance: account 112233445566 region us-east-2 status DELETED
-    Time took to complete stack set operation: 1m 3s
-    Stack set operation completed.
-    Stack Set Operation Summary:
-    account 112233445566 region us-east-1 status SUCCEEDED
-    account 112233445566 region us-east-2 status SUCCEEDED
-    account 223344556677 region us-east-2 status SUCCEEDED
-    account 223344556677 region us-east-1 status SUCCEEDED
-    $

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

@@ -1,23 +0,0 @@
-## Example
-
-    $ lono sets status my-set
-    Stack Set Operation Status: SUCCEEDED
-    Stack Instance statuses... (takes a while)
-    Stack Instance: account 112233445566 region ap-northeast-2 status CURRENT
-    Stack Instance: account 112233445566 region ap-northeast-1 status CURRENT
-    Stack Instance: account 223344556677 region us-west-1 status CURRENT
-    Stack Instance: account 223344556677 region ap-northeast-1 status CURRENT
-    Stack Instance: account 223344556677 region ap-northeast-2 status CURRENT
-    Stack Instance: account 112233445566 region us-west-1 status CURRENT
-    Stack Instance: account 112233445566 region us-west-2 status CURRENT
-    Stack Instance: account 223344556677 region us-west-2 status CURRENT
-    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
-    $

data/lib/lono/help/summary.md

@@ -1,33 +0,0 @@
-The `lono summary` command helps you quickly understand a CloudFormation template.
-
-## Examples
-
-    $ bundle exec lono summary ec2
-    Generating CloudFormation templates for blueprint ec2:
-      output/ec2/templates/ec2-old.yml
-      output/ec2/templates/ec2-new.yml
-    => CloudFormation Template Summary for template ec2-new:
-    Required Parameters (0):
-      There are no required parameters.
-    Optional Parameters (3):
-      InstanceType (String) Default: t3.micro
-      Subnet (String) Default:
-      Vpc (String) Default:
-    Resources:
-      1 AWS::EC2::Instance
-      1 AWS::EC2::SecurityGroup
-      2 Total
-    => CloudFormation Template Summary for template ec2-old:
-    Required Parameters (0):
-      There are no required parameters.
-    Optional Parameters (3):
-      InstanceType (String) Default: t3.micro
-      Subnet (String) Default:
-      Vpc (String) Default:
-    Resources:
-      1 AWS::EC2::Instance
-      1 AWS::EC2::SecurityGroup
-      2 Total
-    $
-
-Blog Post also covers this: [lono summary Tutorial Introduction](https://blog.boltops.com/2017/09/18/lono-inspect-summary-tutorial-introduction)

data/lib/lono/help/template/generate.md

@@ -1,7 +0,0 @@
-## Examples
-
-  lono template generate
-  lono template generate --clean
-  lono template g --clean
-
-Builds the CloudFormation templates files based on lono project and writes them to the output folder on the filesystem.

data/lib/lono/help/upgrade.md

@@ -1 +0,0 @@
-The lono upgrade command works for v6 and onward.

data/lib/lono/help/xgraph.md

@@ -1,16 +0,0 @@
-## Example
-
-With more complex CloudFormation templates, the dependency can get difficult to follow.  Visualizing the dependencies is helpful.
-
-    lono code import https://s3.amazonaws.com/solutions-reference/aws-waf-security-automations/latest/aws-waf-security-automations.template --blueprint waf
-    lono xgraph waf
-
-This above command generates a dependency chart.  The command uses the DependsOn attribute specified in each resource to figure this out.  It does not show implied dependencies that CloudFormaton automatically computes for us.  The chart looks like this:
-
-![](/img/tutorial/waf-chart.png){:.doc-photo}
-
-The chart is generated with [Graphviz](http://www.graphviz.org/). To install:
-
-    brew install graphviz
-
-Blog Post also covers this: [lono inspect depends Tutorial Introduction](https://blog.boltops.com/2017/09/20/lono-inspect-depends-tutorial-introduction)

data/lib/lono/help.rb

@@ -1,15 +0,0 @@
-module Lono::Help
-  class << self
-    # namespaced_command: cfn/create or cfn:create both work.
-    def text(namespaced_command)
-      path = namespaced_command.to_s.gsub(':','/')
-      path = File.expand_path("../help/#{path}.md", __FILE__)
-      IO.read(path) if File.exist?(path)
-    end
-
-    # Generates a markdown file for site docuemtation
-    def markdown
-
-    end
-  end
-end

data/lib/lono/importer/erb.rb

@@ -1,31 +0,0 @@
-class Lono::Importer
-  class Erb < Base
-    def run
-      puts "=> Imported CloudFormation template.".color(:green)
-      template_path = "#{Lono.config.templates_path}/#{@template}.yml"
-      download_template(@source, template_path)
-      puts "Template created: #{pretty_path(template_path)}"
-
-      create_dot_lono("erb")
-      template_definition_path = add_template_definition
-      puts "Template definition added: #{pretty_path(template_definition_path)}"
-
-      create_params(template_path)
-      summarize
-    end
-
-    # Add template definition to app/definitions/base.rb.
-    def add_template_definition
-      path = "#{Lono.config.definitions_path}/base.rb"
-      lines = File.exist?(path) ? IO.readlines(path) : []
-      new_template_definition = %Q|template "#{@template}"|
-      unless lines.detect { |l| l.include?(new_template_definition) }
-        lines << ["\n", new_template_definition]
-        result = lines.join('')
-        FileUtils.mkdir_p(File.dirname(path))
-        IO.write(path, result)
-      end
-      path
-    end
-  end
-end

data/lib/lono/inspector/graph.rb

@@ -1,125 +0,0 @@
-require "yaml"
-require "graph"
-
-module Lono::Inspector
-  class Graph < Base
-    def initialize(options={})
-      super
-      @nodes = [] # lookup map
-    end
-
-    def perform(template)
-      # little dirty but @template is used in data method so we dont have to pass it to the data method
-      @template = template
-
-      puts "Generating dependencies tree for template #{@template}..."
-      return if @options[:noop]
-
-      # First loop through top level nodes and build set depends_on property
-      node_list = [] # top level node list
-      resources = data["Resources"]
-      resources.each do |logical_id, resource|
-        node = Node.new(logical_id)
-        node.depends_on = normalize_depends_on(resource)
-        node.resource_type = normalize_resource_type(resource)
-        node_list << node
-      end
-
-      # Now that we have loop through all the top level resources once
-      # we can use the depends_on attribute on each node and set the
-      # children property since the identity nodes are in memory.
-      node_list.each do |node|
-        node.children = normalize_children(node_list, node)
-      end
-
-      # At this point we have a tree of nodes.
-      if @options[:display] == "text"
-        puts "CloudFormation Dependencies:"
-        node_list.each { |node| print_tree(node) }
-      else
-        print_graph(node_list)
-        puts "CloudFormation Dependencies graph generated."
-      end
-    end
-
-    # normalized DependOn attribute to an Array of Strings
-    def normalize_depends_on(resource)
-      dependencies = resource["DependOn"] || []
-      [dependencies].flatten
-    end
-
-    def normalize_resource_type(resource)
-      type = resource["Type"]
-      type.sub("AWS::", "") # strip out AWS to make less verbose
-    end
-
-    # It is possible with bad CloudFormation templates that the dependency is not
-    # resolved, but we wont deal with that.  Users can validate their CloudFormation
-    # template before using this tool.
-    def normalize_children(node_list, node)
-      kids = []
-      node.depends_on.each do |dependent_logical_id|
-        node = node_list.find { |n| n.name == dependent_logical_id }
-        kids << node
-      end
-      kids
-    end
-
-    def print_tree(node, depth=0)
-      spacing = "  " * depth
-      puts "#{spacing}#{node.name}"
-      node.children.each do |node|
-        print_tree(node, depth+1)
-      end
-    end
-
-    def print_graph(node_list)
-      check_graphviz_installed
-      digraph do
-        # graph_attribs << 'size="6,6"'
-        node_attribs << lightblue << filled
-
-        node_list.each do |n|
-          node(n.graph_name)
-          n.children.each do |child|
-            edge n.graph_name, child.graph_name
-          end
-        end
-
-        random = (0...8).map { (65 + rand(26)).chr }.join
-        path = "/tmp/cloudformation-depends-on-#{random}"
-        save path, "png"
-        # Check if open command exists and use it to open the image.
-        system "open #{path}.png" if system("type open > /dev/null 2>&1")
-      end
-    end
-
-    # Check if Graphiz is installed and prints a user friendly message if it is not installed.
-    # Provide instructions if on macosx.
-    def check_graphviz_installed
-      installed = system("type dot > /dev/null 2>&1") # dot is a command that is part of the graphviz package
-      unless installed
-        puts "It appears that the Graphviz is not installed.  Please install it to generate the graph."
-        if RUBY_PLATFORM =~ /darwin/
-          puts "You can install Graphviz with homebrew:"
-          puts "  brew install brew install graphviz"
-        end
-        exit 1
-      end
-    end
-
-    class Node
-      attr_accessor :name, :resource_type, :children, :depends_on
-      def initialize(name)
-        @name = name
-        @children = []
-        @depends_on = []
-      end
-
-      def graph_name
-        type = "(#{resource_type})" if resource_type
-        [name, type].compact.join("\n")
-      end
-    end
-  end
-end

data/lib/lono/jade/circular.rb

@@ -1,26 +0,0 @@
-class Lono::Jade
-  module Circular
-    def check_for_circular_dependency!
-      circular = circular_dependency?
-      return unless circular
-
-      puts "ERROR: jade circular dependency detected".color(:red)
-      puts "circular dependency: #{parent_names.join(" => ")}"
-      exit 1
-    end
-
-    def circular_dependency?
-      parent_names.uniq.size != parent_names.size
-    end
-
-    def parent_names
-      names = [self.name] # include initial jade name to detect circular dependency earlier
-      parent = registry.parent
-      while parent
-        names << parent.name
-        parent = parent.registry.parent
-      end
-      names
-    end
-  end
-end

data/lib/lono/jade/materializer/final.rb

@@ -1,10 +0,0 @@
-class Lono::Jade::Materializer
-  class Final
-    def build(jades)
-      return if jades.empty?
-      list = jades.map(&:name).uniq.join(", ") # possible to have different versions. only showing names and removing duplicates
-      puts "Materializing #{list}..."
-      GemsBuilder.new(jades).build
-    end
-  end
-end