lono 3.5.0 → 4.0.0

data/lib/lono/completer/script.rb

@@ -0,0 +1,6 @@
+class Lono::Completer::Script
+  def self.generate
+    bash_script = File.expand_path("script.sh", File.dirname(__FILE__))
+    puts "source #{bash_script}"
+  end
+end

data/lib/lono/completer/script.sh

@@ -0,0 +1,10 @@
+_lono() {
+  COMPREPLY=()
+  local word="${COMP_WORDS[COMP_CWORD]}"
+  local words=("${COMP_WORDS[@]}")
+  unset words[0]
+  local completion=$(lono completion ${words[@]})
+  COMPREPLY=( $(compgen -W "$completion" -- "$word") )
+}
+
+complete -F _lono lono

data/lib/lono/completion.rb

@@ -0,0 +1,15 @@
+module Lono
+  class Completion < Command
+    desc "script", "generates script that can be eval to setup auto-completion"
+    long_desc Help.text("completion:script")
+    def script
+      Completer::Script.generate
+    end
+
+    desc "completions *PARAMS", "prints words for auto-completion"
+    long_desc Help.text("completion:list")
+    def list(*params)
+      Completer.new(*params).run
+    end
+  end
+end

data/lib/lono/core.rb

@@ -2,8 +2,11 @@ require 'pathname'
 
 module Lono
   module Core
-    def env
-      LONO_ENV
+    autoload :Config, 'lono/core/config'
+
+    @@config = nil
+    def config
+      @@config ||= Config.new
     end
 
     def root
@@ -11,14 +14,25 @@ module Lono
       Pathname.new(path)
     end
 
-    def setup!
-      settings = Lono::Settings.new.data
-      map = settings['aws_profile_lono_env_map']
-
-      lono_env = map[ENV['AWS_PROFILE']] || map['default'] || 'prod' # defaults to prod
-      lono_env = ENV['LONO_ENV'] if ENV['LONO_ENV'] # highest precedence
+    @@env = nil
+    def env
+      return @@env if @@env
+      ufo_env = env_from_profile(ENV['AWS_PROFILE']) || 'development'
+      ufo_env = ENV['LONO_ENV'] if ENV['LONO_ENV'] # highest precedence
+      @@env = ufo_env
+    end
 
-      Kernel.const_set(:LONO_ENV, lono_env)
+    private
+    # Do not use the Setting class to load the profile because it can cause an
+    # infinite loop then if we decide to use Lono.env from within settings class.
+    def env_from_profile(aws_profile)
+      data = YAML.load_file("#{Lono.root}/config/settings.yml")
+      env = data.find do |_env, setting|
+        setting ||= {}
+        profiles = setting['aws_profiles']
+        profiles && profiles.include?(aws_profile)
+      end
+      env.first if env
     end
   end
 end

data/lib/lono/core/config.rb

@@ -0,0 +1,20 @@
+module Lono::Core
+  class Config
+    PATHS = {
+      definitions_path: "app/definitions",
+      helpers_path: "app/helpers",
+      partials_path: "app/partials",
+      scripts_path: "app/scripts",
+      templates_path: "app/templates",
+      user_data_path: "app/user_data",
+      params_path: "config/params",
+      variables_path: "config/variables",
+      output_path: "output",
+    }
+    PATHS.each do |meth, path|
+      define_method meth do
+        "#{Lono.root}/#{path}"
+      end
+    end
+  end
+end

data/lib/lono/default/settings.yml

@@ -1,13 +1,33 @@
-aws_profile_lono_env_map:
-  default: prod
-  # More examples:
-  # aws_profile1: prod
-  # aws_profile2: stag
-  # aws_profile3: dev
-s3:
-  path:
-    default:  # default is nil
-    # You can specify different buckets for different LONO_ENV.  Examples:
-    # prod: s3://mybucket/templates/storage/path
-    # stag: s3://mybucket/templates/storage/path
-randomize_stack_name: false
+# More info: http://lono.cloud/docs/settings/
+# 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:
+  # http://lono.cloud/docs/app-scripts/
+  # extract_scripts:
+  #   to: "/opt"
+  #   as: "ec2-user"
+  # If s3_folder is set then the generated templates and app/scripts will automatically
+  # be uploaded to s3.
+  # There are 2 formats for s3_folder:
+  # Format 1:
+  # s3_folder: mybucket/path/to/folder # simple string
+  # Format 2:
+  # s3_folder: # Hash options in order to support multiple AWS_PROFILEs
+  #   default: mybucket/folder
+  #   aws_profile1: mybucket/folder
+  #   aws_profile2: another-bucket/storage/folder
+  # randomize_stack_name: true # tack on a 3 char random string at the end of the stack name for lono cfn create
+
+
+development:
+  # When you have AWS_PROFILE set to one of these values, lono will switch to the desired
+  # environment. This prevents you from switching AWS_PROFILE, forgetting to
+  # also switch LONO_ENV, and accidentally deploying to production vs development.
+  # aws_profiles:
+  #   - dev_profile1
+  #   - dev_profile2
+
+production:
+  # aws_profiles:
+  #   - prod_profile

data/lib/lono/help.rb

@@ -1,82 +1,9 @@
 module Lono::Help
-  def new_long_desc
-<<-EOL
-Examples:
-
-$ lono new project
-
-$ lono new lono
-EOL
+  class << self
+    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
   end
-
-  def import
-<<-EOL
-Examples:
-
-$ lono import /path/to/file
-
-$ lono import http://url.com/path/to/template.json
-
-$ lono import http://url.com/path/to/template.yml
-
-Imports a raw CloudFormation template and lono-fies it.
-EOL
-  end
-
-  def generate
-<<-EOL
-Examples:
-
-$ lono generate
-
-$ lono g -c # shortcut
-
-Builds both CloudFormation template and parameter files based on lono project and writes them to the output folder on the filesystem.
-EOL
-  end
-
-  def template
-<<-EOL
-Examples:
-
-$ lono template generate --help
-
-$ lono template bashify --help
-EOL
-
-  end
-
-  def cfn
-<<-EOL
-Examples:
-
-$ lono cfn create my-stack
-
-$ lono cfn preview my-stack
-
-$ lono cfn update my-stack
-
-$ lono cfn delete my-stack
-EOL
-  end
-
-  def param
-<<-EOL
-Examples:
-
-$ lono param generate
-EOL
-  end
-
-  def inspector
-<<-EOL
-Examples:
-
-$ lono inspect depends my-stack
-
-$ lono inspect summary my-stack
-EOL
-  end
-
-  extend self
 end

data/lib/lono/help/cfn.md

@@ -0,0 +1,6 @@
+Examples:
+
+  lono cfn create my-stack
+  lono cfn preview my-stack
+  lono cfn update my-stack
+  lono cfn delete my-stack

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

@@ -0,0 +1,22 @@
+Examples:
+
+Provided that you are in a lono project and have a `my-stack` lono template definition.  To create a stack you can simply run:
+
+  lono cfn create my-stack
+
+The above command will generate and use the template in output/my-stack.json and parameters in params/my-stack.txt.  The template by convention defaults to the name of the stack.  In turn, the params by convention defaults to the name of the template.
+
+Here are examples of overriding the template and params name conventions.
+
+  lono cfn create my-stack --template different1
+
+The template used is output/different1.json and the parameters used is output/params/prod/different1.json.
+
+  lono cfn create my-stack --params different2
+
+The template used is output/my-stack.json and the parameters used is output/params/prod/different2.json.
+
+  lono cfn create my-stack --template different3 --params different4
+
+The template used is output/different3.json and the parameters used is output/params/prod/different4.json.
+

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

@@ -0,0 +1,5 @@
+Examples:
+
+  lono cfn delete my-stack
+
+The above command will delete my-stack.

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

@@ -0,0 +1,5 @@
+Displays code diff of the generated CloudFormation template locally vs the existing template on AWS. You can set a desired diff viewer by setting the LONO_CFN_DIFF environment variable.
+
+Examples:
+
+  lono cfn diff my-stack

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

@@ -0,0 +1,5 @@
+Download CloudFormation template from existing template on AWS.
+
+Examples:
+
+  lono cfn download my-stack

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

@@ -0,0 +1,11 @@
+Generates a CloudFormation preview.  This is similar to a `terraform plan` or puppet's dry-run mode.
+
+Example output:
+
+CloudFormation preview for 'example' stack update. Changes:
+
+Remove AWS::Route53::RecordSet: DnsRecord testsubdomain.sub.tongueroo.com
+
+Examples:
+
+  lono cfn preview my-stack

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

@@ -0,0 +1,21 @@
+Examples:
+
+Provided that you are in a lono project and have a `my-stack` lono template definition.  To update a stack you can simply run:
+
+  lono cfn update my-stack
+
+The above command will generate and use the template in output/my-stack.json and parameters in params/my-stack.txt.  The template by convention defaults to the name of the stack.  In turn, the params by convention defaults to the name of the template.
+
+Here are examples of overriding the template and params name conventions.
+
+  lono cfn update my-stack --template different1
+
+The template used is output/different1.json and the parameters used is output/params/prod/different1.json.
+
+  lono cfn update my-stack --params different2
+
+The template used is output/my-stack.json and the parameters used is output/params/prod/different2.json.
+
+  lono cfn update my-stack --template different3 --params different4
+
+The template used is output/different3.json and the parameters used is output/params/prod/different4.json.

data/lib/lono/help/completion.md

@@ -0,0 +1,22 @@
+Example:
+
+  lono completion
+
+Prints words for TAB auto-completion.
+
+Examples:
+
+  lono completion
+  lono completion hello
+  lono completion hello name
+
+To enable, TAB auto-completion add the following to your profile:
+
+  eval $(lono completion script)
+
+Auto-completion example usage:
+
+  lono [TAB]
+  lono hello [TAB]
+  lono hello name [TAB]
+  lono hello name --[TAB]

data/lib/lono/help/completion_script.md

@@ -0,0 +1,3 @@
+To use, add the following to your ~/.bashrc or ~/.profile
+
+  eval $(lono completion script)

data/lib/lono/help/generate.md

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

data/lib/lono/help/hello.md

@@ -0,0 +1,5 @@
+Examples:
+
+  lono hello
+  lono hello NAME
+  lono hello NAME --from me

data/lib/lono/help/import.md

@@ -0,0 +1,7 @@
+Examples:
+
+  lono import /path/to/file
+  lono import http://url.com/path/to/template.json
+  lono import http://url.com/path/to/template.yml
+
+Imports a raw CloudFormation template and lono-fies it.

data/lib/lono/help/inspect.md

@@ -0,0 +1,4 @@
+Examples:
+
+  lono inspect depends my-stack
+  lono inspect summary my-stack

data/lib/lono/help/inspect/depends.md

@@ -0,0 +1,3 @@
+Example:
+
+  lono inspect depends my-stack

data/lib/lono/help/inspect/summary.md

@@ -0,0 +1,3 @@
+Example:
+
+  lono inspect summary my-stack

data/lib/lono/help/new.md

@@ -0,0 +1,8 @@
+Examples:
+
+  lono new infra # skeleton project with barebones structure
+  TEMPLATE=ec2 lono new infra # creates a single server
+  TEMPLATE=autoscaling lono new infra
+
+For a list of the starter templates:
+https://github.com/tongueroo/lono/tree/master/lib/starter_projects

data/lib/lono/help/param.md

@@ -0,0 +1,3 @@
+Examples:
+
+  lono param generate

data/lib/lono/{param/help.rb → help/param/generate.md}

@@ -1,15 +1,7 @@
-class Lono::Param::Help
-  class << self
-    def generate
-<<-EOL
 Example:
 
 To generate a CloudFormation json parameter files in the params folder to the output/params folder.
 
-$ lono-params generate
+  lono-params generate
 
 If you have params/my-stack.txt. It will generate a CloudFormation json file in output/params/my-stack.json.
-EOL
-    end
-  end
-end

data/lib/lono/help/script/build.md

@@ -0,0 +1,5 @@
+Builds output/scripts/scripts-md5sum.tgz from app/script folder.
+
+Examples:
+
+  lono script build