forger 2.0.3 → 2.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6551f0c2a373f261855464a53423a8857597d5defde345906c85d6bad2bb9a25
-  data.tar.gz: b9e2d641ffd5ecb2c2c738f344457f5206a0b135b4651db524cbfccaf42ae594
+  metadata.gz: 87afc9047bd6ddfd919e409829ff4a41eb4e4278a9b49f8e4ed2d4203392aa20
+  data.tar.gz: 1f57d952114627db436d8c66847fcfd297138b8741090388a4a96dd5cb7f77c4
 SHA512:
-  metadata.gz: 1285b67f2407a48b432f8da375e32ec78bdad5b376ae3ddd5895d54700102df5a2f41a8fbe33cc989c32fb0e0af498ef4d0fe85f3b29209af75e2190d3bbb01f
-  data.tar.gz: 900c2a261d3db83789abdac6587b09b9ce57bb2cff977cebf48acf9e082934861d8844a9911893da5a498080c9b7dc09b5198fcc66e299d39c369ed1da742993
+  metadata.gz: 6eea81c540ba1eaf35aa6ce7cc5e6308019ca4eb6927664380c1029a2458122577c26c8357c02838625781b428b52bd859000bafd043376cc4ac4cf6f273edc0
+  data.tar.gz: a1d92f74984329a186d0e7bee07f9ad60adb3277737f81e9b2c80c67e51723a63fa9a78671abdae3ca85d13ac3a5f0f02325fd8fcfbd4d4619cf782635c8b265

data/CHANGELOG.md

@@ -3,6 +3,9 @@
 All notable changes to this project will be documented in this file.
 This project *tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
 
+## [2.0.4]
+- Merge pull request #15 from tongueroo/tmp-write-area: move write operations to /tmp area
+
 ## [2.0.3]
 - fix noop option for s3 upload
 - remove -eux bash flags to quiet scripts

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    forger (2.0.3)
+    forger (2.0.4)
       activesupport
       aws-sdk-ec2
       aws-sdk-s3
@@ -22,7 +22,7 @@ GEM
       minitest (~> 5.1)
       tzinfo (~> 1.1)
     aws-eventstream (1.0.1)
-    aws-partitions (1.123.0)
+    aws-partitions (1.125.0)
     aws-sdk-core (3.44.0)
       aws-eventstream (~> 1.0)
       aws-partitions (~> 1.0)
@@ -42,7 +42,7 @@ GEM
     byebug (10.0.2)
     coderay (1.1.2)
     colorize (0.8.1)
-    concurrent-ruby (1.1.3)
+    concurrent-ruby (1.1.4)
     diff-lcs (1.3)
     dotenv (2.5.0)
     ffi (1.9.25)
@@ -87,8 +87,8 @@ GEM
       method_source (~> 0.9.0)
     rake (12.3.2)
     rb-fsevent (0.10.3)
-    rb-inotify (0.9.10)
-      ffi (>= 0.5.0, < 2)
+    rb-inotify (0.10.0)
+      ffi (~> 1.0)
     render_me_pretty (0.8.1)
       activesupport
       colorize
@@ -127,4 +127,4 @@ DEPENDENCIES
   rake
 
 BUNDLED WITH
-   1.17.1
+   1.17.2

data/README.md

@@ -38,7 +38,7 @@ Notably, using the `--s3-folder` option generates a project that make use of the
 You can do a test run with the `--noop` flag.  This will print out what settings will be used to launch the instance.  This is one good way to inspect the generated user-data script.
 
     forger create myserver --profile myserver --noop
-    cat tmp/user-data.txt # to view generated user-data script
+    cat /tmp/forger/ec2/user-data.txt # to view generated user-data script
 
 ## Conventional Profile Name
 
@@ -94,7 +94,7 @@ You can provide a user-data script to customize the server upon launch.  The use
 The user-data script is generated on the machine that is running the forger command. If this is your local macosx machine, then the context of your local macosx machine is available. To see the generated user-data script, you can run the create command in `--noop` mode and then inspect the generated script.  Example:
 
     forger create myserver --noop
-    cat tmp/user-data.txt
+    cat /tmp/forger/ec2/user-data.txt
 
 Another way to view the generated user-data scripts is the `forger compile` command.  It generates the files in the `tmp` folder.  Example:
 

data/lib/forger/base.rb

@@ -1,8 +1,8 @@
 module Forger
   class Base
     # constants really only used by script classes
-    SCRIPTS_INFO_PATH = "tmp/data/scripts_info.txt"
-    BUILD_ROOT = "tmp"
+    BUILD_ROOT = "/tmp/forger/#{File.basename(Dir.pwd)}"
+    SCRIPTS_INFO_PATH = "#{BUILD_ROOT}/data/scripts_info.txt"
 
     def initialize(options={})
       @options = options.clone

data/lib/forger/core.rb

@@ -40,6 +40,10 @@ module Forger
       @@env = env
     end
 
+    def build_root
+      Base::BUILD_ROOT
+    end
+
     private
     # Do not use the Setting class to load the profile because it can cause an
     # infinite loop then if we decide to use Forger.env from within settings class.

data/lib/forger/create/info.rb

@@ -122,7 +122,7 @@ class Forger::Create
       data = data.deep_stringify_keys
 
       if data["user_data"]
-        message = "base64-encoded: cat tmp/user-data.txt to view"
+        message = "base64-encoded: cat #{Forger.build_root}/user-data.txt to view"
         data["user_data"] = message
       end
 

data/lib/forger/profile.rb

@@ -28,7 +28,8 @@ module Forger
       begin
         data = YAML.load(text)
       rescue Psych::SyntaxError => e
-        tmp_file = file.sub("profiles", "tmp")
+        tmp_file = file.sub("profiles", Forger.build_root)
+        FileUtils.mkdir_p(File.dirname(tmp_file))
         IO.write(tmp_file, text)
         puts "There was an error evaluating in your yaml file #{file}".colorize(:red)
         puts "The evaludated yaml file has been saved at #{tmp_file} for debugging."

data/lib/forger/template/helper/core_helper.rb

@@ -24,7 +24,7 @@ module Forger::Template::Helper::CoreHelper
     result = scripts.join(divider)
 
     # save the unencoded user-data script for easy debugging
-    temp_path = "#{Forger.root}/tmp/user-data.txt"
+    temp_path = "#{Forger.build_root}/user-data.txt"
     FileUtils.mkdir_p(File.dirname(temp_path))
     IO.write(temp_path, result)
 

data/lib/forger/version.rb

@@ -1,3 +1,3 @@
 module Forger
-  VERSION = "2.0.3"
+  VERSION = "2.0.4"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: forger
 version: !ruby/object:Gem::Version
-  version: 2.0.3
+  version: 2.0.4
 platform: ruby
 authors:
 - Tung Nguyen
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-12-12 00:00:00.000000000 Z
+date: 2018-12-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport