lono 7.5.2 → 8.0.0.pre.rc3

data/lib/lono/finder/base.rb

@@ -1,152 +0,0 @@
-require "bundler"
-require "text-table"
-
-module Lono::Finder
-  class Base
-    extend Memoist
-
-    def initialize(lono_root: nil, blueprint_root: nil)
-      @lono_root = lono_root || Lono.root
-      @blueprint_root = blueprint_root || Lono.blueprint_root
-    end
-
-    # Returns root path of component: blueprint or configset
-    def find(name, local_only: false)
-      all = find_all(local_only: local_only)
-      all.find { |jadespec| jadespec.name == name }
-    end
-
-    def find_all(local_only: false)
-      if local_only
-        local
-      else
-        local + materialized
-      end
-    end
-
-    def local
-      project + vendor + gems
-    end
-
-    def project
-      roots = path_roots("#{@lono_root}/app/#{type.pluralize}")
-      components(roots, "project")
-    end
-
-    def vendor
-      roots = path_roots("#{@lono_root}/vendor/#{type.pluralize}")
-      components(roots, "vendor")
-    end
-
-    def gems
-      components(gem_roots, "gem")
-    end
-
-    # Folders that each materialized gems to tmp/jades
-    def materialized
-      components(materialized_gem_roots, "materialized")
-    end
-
-    # Components: blueprints or configsets
-    # Returns array of config Hashes. Example structure:
-    #
-    #     [{
-    #       name: "cfn-hup",
-    #       root: "/path/to/gem/root",
-    #       source_type: "project",
-    #     },...]
-    #
-    def components(roots, source_type)
-      components = []
-      roots.each do |root|
-        next unless detect?(root)
-        jadespec = Lono::Jadespec.new(root, source_type)
-        components << jadespec
-      end
-      components
-    end
-    memoize :components
-
-    def detect?(root)
-      expr = "#{root}/#{detection_path}"
-      Dir.glob(expr).size > 0
-    end
-
-    # Used for blueprints, configsets, and blueprint/configsets
-    def list(options={})
-      table = Text::Table.new
-      table.head = ["Name", "Path", "Type"]
-
-      components = find_all.sort_by { |jadespec| jadespec.name }
-      components.each do |jadespec|
-        pretty_path = jadespec.root.sub("#{Lono.root}/", "").sub(ENV['HOME'], "~")
-        unless options[:filter_materialized] && jadespec.source_type == "materialized"
-          table.rows << [jadespec.name, pretty_path, jadespec.source_type]
-        end
-      end
-
-      if table.rows.empty?
-        puts "No #{type.pluralize} found."
-      else
-        puts(options[:message] || "Available #{type.pluralize}:")
-        puts table
-      end
-    end
-
-  private
-    def path_roots(path)
-      Dir.glob("#{path}/*").to_a
-    end
-
-    # Example return:
-    #
-    #     [
-    #       "/home/ec2-user/.rbenv/versions/2.5.6/lib/ruby/gems/2.5.0/gems/rake-13.0.1",
-    #       "/home/ec2-user/.rbenv/versions/2.5.6/lib/ruby/gems/2.5.0/gems/thor-0.20.3"
-    #     ]
-    #
-    def gem_roots
-      Bundler.load.specs.map do |spec|
-        spec.full_gem_path
-      end
-    end
-    memoize :gem_roots
-
-    def materialized_gem_roots
-      gemfile_lock = "#{Lono.root}/tmp/jades/Gemfile.lock"
-      return [] unless File.exist?(gemfile_lock)
-
-      parser = Bundler::LockfileParser.new(Bundler.read_file(gemfile_lock))
-      specs = parser.specs
-      # __materialize__ only exists in Gem::LazySpecification and not in Gem::Specification
-      specs.each { |spec| spec.__materialize__ }
-      begin
-        specs.map do |spec|
-          spec.full_gem_path
-        end
-      rescue RuntimeError => e
-        if e.message.include?("LazySpecification has not been materialized yet")
-          # Thinking quiet behavior is preferred. Leaving comment here for now.
-          # puts "WARN: The Finder class is having trouble using the cached tmp/jades/Gemfile.lock to search for materialized gems."
-          # puts "This can happen when materialized gems are updated. It is generally safe to ignore."
-          # puts "To remove this warning you can remove the cached Gemfile.lock"
-          return []
-        else
-          raise(e)
-        end
-      end
-    end
-    memoize :materialized_gem_roots
-
-  public
-    class << self
-      def find(name)
-        new.find(name)
-      end
-
-      def list(options={})
-        new.list(options)
-      end
-    end
-  end
-end

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

@@ -1,17 +0,0 @@
-class Lono::Finder::Blueprint
-  class Configset < Lono::Finder::Configset
-    def initialize(options={})
-      super(**options) # **options to remove: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
-      @blueprint_root = options[:blueprint_root] || Lono.blueprint_root
-    end
-
-    def local
-      project + vendor + blueprint_app + gems
-    end
-
-    def blueprint_app
-      roots = path_roots("#{@blueprint_root}/app/#{type.pluralize}")
-      components(roots, "blueprint")
-    end
-  end
-end

data/lib/lono/finder/blueprint.rb

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

data/lib/lono/finder/configset.rb

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

data/lib/lono/finder/extension.rb

@@ -1,11 +0,0 @@
-module Lono::Finder
-  class Extension < Base
-    def type
-      "extension"
-    end
-
-    def detection_path
-      "lib/*/helpers"
-    end
-  end
-end

data/lib/lono/generate.rb

@@ -1,111 +0,0 @@
-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 unless generate_only?
-      pre_generate
-      generate_templates # generates with some placeholders for build_files IE: file://app/files/my.rb
-      post_generate
-      upload unless generate_only?
-
-      @@parameters = param_generator.generate  # Writes the json file in CamelCase keys format
-      check_for_errors
-      @@parameters
-    end
-
-    def generate_only?
-      ENV['LONO_GENERATE_ONLY'] || @options[:generate_only]
-    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
-    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
-      Lono::Configset::S3File::Build.new(@options).run # copies files to the output folder
-    end
-
-    def generate_templates
-      Lono::Template::Generator.new(@options).run # write templates to disk
-      inject_configsets
-    end
-
-    def inject_configsets
-      # The inject_configsets reads it back from disk. Leaving as-is instead of reading all in memory in case there's a reason.
-      Lono::Configset::Preparer.new(@options).run # register and materialize gems
-      Lono::Template::ConfigsetInjector.new(@options).run
-    end
-
-    def post_process_template
-      Lono::Template::PostProcessor.new(@options).run
-    end
-
-    def upload
-      upload_files
-      upload_scripts
-      upload_templates
-    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
-      Lono::Configset::S3File::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/cfn/create.md

@@ -1,26 +0,0 @@
-## 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:
-
-    lono cfn create 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 create 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 create 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 create 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/delete.md

@@ -1,13 +0,0 @@
-## Examples
-
-    $ lono cfn delete ec2
-    Are you sure you want to delete the stack? (y/N)
-    y
-    Deleted example stack.
-    $
-
-Lono prompts you with an "Are you sure?" message before the stack gets deleted.  If you would like to bypass the prompt, you can use the `--sure` flag.
-
-    $ lono cfn delete example --sure
-    Deleted example stack.
-    $

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

@@ -1,21 +0,0 @@
-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
-
-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:
-
-    lono cfn deploy demo
-
-The above command will generate:
-
-* template:   output/demo/templates/demo.yml
-* parameters: output/demo/params/development.json
-
-
-## Conventions
-
-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`.
-
-Often you want to create a stack name that is different from the blueprint name. Here’s an example of overriding the blueprint name.
-
-    lono cfn deploy my-stack --blueprint demo

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

@@ -1,3 +0,0 @@
-## Examples
-
-  lono cfn download my-stack

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/seed.md

@@ -1,23 +0,0 @@
-## Example
-
-    $ lono seed ecs-asg
-    Creating starter config files for ecs-asg
-          create  configs/ecs-asg/params/development.txt
-    $ cat configs/ecs-asg/params/development.txt
-    # Required parameters:
-    VpcId=vpc-111 # Find at vpc CloudFormation Outputs
-    Subnets=subnet-111,subnet-222,subnet-333 # Find at vpc CloudFormation Outputs
-    # Optional parameters:
-    # InstanceType=m5.large
-    # KeyName=...
-    # SshLocation=...
-    # EcsCluster=development
-    # TagName=ecs-asg-development
-    # ExistingIamInstanceProfile=...
-    # ExistingSecurityGroups=...
-    # EbsVolumeSize=50
-    # MinSize=1
-    # MaxSize=4
-    # MinInstancesInService=2
-    # MaxBatchSize=1
-    $

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

@@ -1,21 +0,0 @@
-## Example
-
-    $ lono set_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/set_instances/deploy.md

@@ -1,31 +0,0 @@
-The deploy command delegates to the `lono set_instances create` or `lono set_instances update` commands. This spares you from having to manually figuring out which stack instances need to be created and updated.
-
-## Example
-
-    $ lono set_instances deploy enable-aws-config --accounts 111111111111 222222222222 --regions us-west-2 us-east-2Running lono set_instances create on account: 111111111111 regions: us-west-2,us-east-2
-    Deploying enable-aws-config stack set
-    Stack Set Operation Status: RUNNING
-    Stack Instance statuses... (takes a while)
-    You can also check with StackSets console at the Operations Tab.
-    Here is also the cli command to check:
-
-        aws cloudformation describe-stack-set-operation --stack-set-name enable-aws-config --operation-id 44a50065-1b10-49f0-b6b9-853092a0cb09
-
-    2020-04-25 10:58:32PM Stack Instance: account 222222222222 region us-east-2 status CURRENT
-    2020-04-25 10:58:32PM Stack Instance: account 111111111111 region us-west-2 status OUTDATED reason User initiated operation
-    2020-04-25 10:58:32PM Stack Instance: account 222222222222 region us-west-2 status CURRENT
-    2020-04-25 10:58:32PM Stack Instance: account 111111111111 region us-east-2 status OUTDATED reason User initiated operation
-    Stack Set Operation Status: SUCCEEDED
-    Time took to complete stack set operation: 1m 23s
-    Stack Set Operation Summary:
-    account 111111111111 region us-west-2 status SUCCEEDED
-    account 111111111111 region us-east-2 status SUCCEEDED
-    Running lono set_instances update on account: 222222222222 regions: us-west-2,us-east-2
-    Deploying enable-aws-config stack set
-    Stack Set Operation Status: RUNNING
-    Stack Set Operation Status: SUCCEEDED
-    Time took to complete stack set operation: 23s
-    Stack Set Operation Summary:
-    account 222222222222 region us-west-2 status SUCCEEDED
-    account 222222222222 region us-east-2 status SUCCEEDED
-    $

data/lib/lono/help/set_instances/list.md

@@ -1,14 +0,0 @@
-## Example
-
-    $ lono set_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/set_instances/status.md

@@ -1,15 +0,0 @@
-## Example
-
-    $ lono set_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.
-    $