cloudformation-tool 1.3.4 → 1.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5e68236a0ceae7d8423b08ad878d8800398f6f3d4035883961369db5cce9e69a
-  data.tar.gz: 2f0d5633efd0cd1a20caa428135e1e81f483855dfa77dedaabc9d3b8657a2d01
+  metadata.gz: 818f632bb0756f9be2ba922936b2a68e93a12d3af1a10b069e48941dd0615cfd
+  data.tar.gz: 612c5e90b2a95f54435e1ddcbd65a4f833863097c61709a7d9d6895dd041c91e
 SHA512:
-  metadata.gz: cfc5b645933403a7ec6b66151bcd0bb47e74324573ebe61455cbe10505e46c1ff7867960fd108b91f9a6302da8ae165ddd981f633f96175a149a74fcae6b8e70
-  data.tar.gz: 0ea95fa0ca26a6b3106f7ecd31b659025f7d7f7d76d15d0b19fd47475102135883165c5e8e655a4ceadade2ddde17ecf65fea73a1771a4a8c34f45d6f85f11b4
+  metadata.gz: ed6cb8daf2f5990b0a0df87149f9537e29153aacaa65c81a73fee2f2dc05e7d882a99463c22e1fafb00f46757961418df392e730cca805783922ad62db6114ba
+  data.tar.gz: 9d584621509bf30401687ca5c946d9dd45d38a9ad6454b929283099db0ed2ae2aa4ddf93eecf2e123936c4c0a98c605bbe9bfb38c44609c94d4b06e09f626cb1

data/README.md

@@ -103,27 +103,30 @@ multiple sub-templates, this is an error that would cause the tool to abort.
 
 ### Loading user data files
 
-When specifying a user-data block for a `LaunchConfiguration` resource or an `Instance`
-resource, the user-data can be loaded from an external YAML file (only YAML formatted user-data
-is currently supported, sorry) by specifying the `UserData` element as a map with the single
-field `File` that is set with the relative path to the user-data file. The user-data file is
-expected to be a cloud-init configuration file with the default extension `.init`.
-
-Alternatively, the field `FileTemplate` can be used under `UserData` to load an external cloud-init configuration file that includes variable place holders for the
-(CloudFormation intrinsic function Sub)[http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-sub.html]. The `FileTemplate` mode supports all
-the features described above as well as it performs the parsing detailed below, except
-compression and S3 offloading - as doing so prevents CloudFormation from performing the
-substitution operation. As a result, if the resulting cloud-init file is larger than 16KB
-you should expect that the template will fail to create the server.
+When specifying a user-data block for a `LaunchConfiguration` resource, `Instance`
+resource, or a `LaunchTemplate` resource, the user-data can be loaded from an external
+YAML file (only YAML formatted user-data is currently supported, sorry) by specifying the
+`UserData` element as a map with the single field `File` that is set with the relative
+path to the user-data file. The user-data file is expected to be a cloud-init configuration
+file with the default extension `.init` (but there really aren't any filename requirements).
+
+Alternatively, the field `FileTemplate` can be used under `UserData` to load an external
+cloud-init configuration file that includes variable place holders for the
+(CloudFormation intrinsic function Sub)[http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-sub.html].
+The `FileTemplate` mode supports all the features described above as well as it performs
+the parsing detailed below, except compression and S3 offloading - as doing so prevents
+CloudFormation from performing the substitution operation. As a result, if the resulting
+cloud-init file is larger than 16KB you should expect that the template will fail to create
+the stack.
 
 #### User data file parsing
 
 The reference file will be loaded and parsed as a ("Cloud Config data" file)[http://cloudinit.readthedocs.io/en/latest/topics/format.html#cloud-config-data]
-with the special `write_files` and `write_directories` enhancement (see below). The result is then checked that it
-does not exceed the user-data size limitation. If the file is bigger than can fit in the AWS
-user-data block, it will first be compressed using gzip and if it is still too large, it will
-be uploaded to S3 and the user-data block will be set with a cloud-init download reference to
-the S3 object.
+with the special `write_files` and `write_directories` enhancement (see below). 
+The result is then checked that it does not exceed the user-data size limitation.
+If the file is bigger than can fit in the AWS user-data block, it will first be compressed
+using gzip and if it is still too large, it will be uploaded to S3 and the user-data block
+will be set with a cloud-init download reference to the S3 object.
 
 ##### Enhanced `write_files`
 

data/lib/cloud_formation_tool/cloud_formation.rb

@@ -23,7 +23,7 @@ module CloudFormationTool
       begin
         text = File.read(@path)
         # remove comments because white space seen between comments can seriously psych Psych
-        text.gsub!(/^#.*\n/s,'')
+        text.gsub!(/^#.*\n/,'')
         text = fixShorthand(text)
         @data = YAML.load(text).to_h
       rescue Psych::SyntaxError => e
@@ -167,7 +167,7 @@ module CloudFormationTool
         restype = data['Type'] if restype.nil? and data.key?('Type')
         data.inject({}) do |dict, (key, val)|
           dict[key] = case restype
-            when 'AWS::AutoScaling::LaunchConfiguration'
+            when 'AWS::AutoScaling::LaunchConfiguration', 'AWS::EC2::LaunchTemplate'
               if (key == "UserData") and (val["File"]) 
                 # Support LaunchConfiguration UserData from file
                 CloudInit.new("#{@basedir}/#{val["File"]}").to_base64

data/lib/cloud_formation_tool/version.rb

@@ -1,3 +1,3 @@
 module CloudFormationTool
-  VERSION = '1.3.4'
+  VERSION = '1.4.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cloudformation-tool
 version: !ruby/object:Gem::Version
-  version: 1.3.4
+  version: 1.4.0
 platform: ruby
 authors:
 - Oded Arbel
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2020-07-07 00:00:00.000000000 Z
+date: 2021-01-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake