sparkle-guides 0.1.4 → 0.1.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b6d84bfd1702300758e47d0348e9905a0d70c0f8
-  data.tar.gz: c2a02647503ca0fd162e28a3c33bae7cb2c53e81
+  metadata.gz: 1f04bb4a6026891d6f8c468a1c6e880238605994
+  data.tar.gz: b8f10b89284f3390ec13ea9e648be1f33ff5765f
 SHA512:
-  metadata.gz: 824eba256e15ac401704765d07500313c61fa7930637992f9bf793d03978c88e0922b5059e3757f345b21a65af082de1c9f2ea7009684ed23cc5ea9c9d7a4031
-  data.tar.gz: e76f5398b1baa00c49d3abf332662e63c5ca4bcf36474cb9b524daead8418fa9baa690a5f47b124f3e3186f5ded5a414104c18afe682302d7b3cc5e8f17e8d8f
+  metadata.gz: 609346d36b4974a68eab22b9c0b308ab9e2a5efc7f7dde88ea31e580cab963c63f073bf46b302fbfd731644ad49cd2acccb083d6722844fb192d95836f82cd3f
+  data.tar.gz: 58fd492797e2c62431f922dd68671b40b995a2e70ca94a0001dcbc2488c2c0853cf6319178225ce536b60131117c8b130cff6a03bb4067bacfb3021a0e879850

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+# v0.1.6
+* Fixes for syntax, instructions, and removal of m1 types (#8)
+ * Thanks @rberger!
+
 # v0.1.4
 * Update file system layout.
 * Fix YAML error on guide header.

data/docs/apply-and-nested.md

@@ -83,7 +83,7 @@ SparkleFormation.new(:network) do
 
   dynamic!(:ec2_vpc, :network) do
     properties do
-      cidr_block join!(ref!(:cidr_prefix, '.0.0/24'))
+      cidr_block join!(ref!(:cidr_prefix), '.0.0/24')
       enable_dns_support true
       enable_dns_hostnames true
     end
@@ -127,7 +127,7 @@ SparkleFormation.new(:network) do
   dynamic!(:ec2_subnet, :network) do
     properties do
       availability_zone select!(0, azs!)
-      cidr_block join!(ref!(:cidr_prefix, '.0.0/24'))
+      cidr_block join!(ref!(:cidr_prefix), '.0.0/24')
       vpc_id ref!(:network_ec2_vpc)
     end
   end
@@ -143,7 +143,7 @@ SparkleFormation.new(:network) do
     network_vpc_id.value ref!(:network_ec2_vpc)
     network_subnet_id.value ref!(:network_ec2_subnet)
     network_route_table.value ref!(:network_ec2_route_table)
-    network_cidr.value join!(ref!(:cidr_prefix, '.0.0/24'))
+    network_cidr.value join!(ref!(:cidr_prefix), '.0.0/24')
   end
 
 end
@@ -173,6 +173,10 @@ SparkleFormation.new(:computes) do
     ssh_key_name.type 'String'
     network_vpc_id.type 'String'
     network_subnet_id.type 'String'
+    image_id_name do
+        type 'String'
+        default 'ami-63ac5803'
+    end
   end
 
   dynamic!(:ec2_security_group, :compute) do
@@ -190,8 +194,8 @@ SparkleFormation.new(:computes) do
 
   dynamic!(:ec2_instance, :micro) do
     properties do
-      image_id 'ami-25c52345'
-      image_type 't2.micro'
+      image_id ref!(:image_id_name)
+      instance_type 't2.micro'
       key_name ref!(:ssh_key_name)
       network_interfaces array!(
         ->{
@@ -206,8 +210,8 @@ SparkleFormation.new(:computes) do
 
   dynamic!(:ec2_instance, :small) do
     properties do
-      image_id 'ami-25c52345'
-      image_type 't2.micro'
+      image_id ref!(:image_id_name)
+      instance_type 't2.micro'
       key_name ref!(:ssh_key_name)
       network_interfaces array!(
         ->{
@@ -277,6 +281,13 @@ During the create process, the SparkleFormation CLI will prompt for parameters.
 default values for the VPC ID and subnet ID will be automatically inserted, matching
 the outputs from the `sparkle-guide-network`.
 
+You can destroy the sparkle-guide-compute and sparkle-guide-network stacks as they will not be used in the next section.
+
+~~~
+$ sfn destroy sparkle-guide-computes
+$ sfn destroy sparkle-guide-network
+~~~
+
 ## Nested stack implementation
 
 Now that our infrastructure has been successfully created using disparate stacks, lets
@@ -372,4 +383,10 @@ $ bundle exec sfn create sparkle-guide-computes-infra --file computes --apply-st
 ~~~
 
 The ability to apply nested stacks to disparate stacks make it easy to provide resources to new
-stacks, or to test building new stacks in isolation before being nested into the root stack.
+stacks, or to test building new stacks in isolation before being nested into the root stack.
+
+You can destroy the all the `infrastructure` related stacks with the command:
+
+~~~
+sfn destroy sparkle-guide-infrastructure
+~~~

data/docs/getting-started.md

@@ -160,7 +160,7 @@ SparkleFormation.new(:compute, :provider => :heat) do
     sparkle_ssh_key_name.type 'String'
     sparkle_flavor do
       type 'String'
-      default 'm1.small'
+      default 't2.small'
       allowed_values ['m1.small', 'm1.medium']
     end
   end
@@ -334,7 +334,7 @@ Create a new file at `./sparkleformation/registry/instance_flavor.rb`
 
 ~~~ruby
 SfnRegistry.register(:instance_flavor) do
-  ['m1.small', 'm1.medium']
+  ['t2.micro', 't2.small']
 end
 ~~~
 
@@ -411,7 +411,7 @@ SparkleFormation.dynamic(:node) do |name, opts={}|
     set!("#{name}_ssh_key_name".to_sym).type 'String'
     set!("#{name}_flavor".to_sym) do
       type 'String'
-      default 'm1.small'
+      default 't2.small'
       allowed_values registry!(:instance_flavor)
     end
   end
@@ -442,7 +442,7 @@ SparkleFormation.dynamic(:node) do |name, opts={}|
     set!("#{name}_ssh_key_name".to_sym).type 'String'
     set!("#{name}_flavor".to_sym) do
       type 'String'
-      default 'm1.small'
+      default 't2.small'
       allowed_values registry!(:instance_flavor)
     end
   end
@@ -623,14 +623,21 @@ The `--defaults` flag will suppress prompts for stack parameters and use the exi
 stack. The result of this command will either explicitly state that no updates were performed, or the event stream
 will show that no resources were modified depending on the provider.
 
+At the end of the run it will ask:
+
+~~~
+[Sfn]: Apply this stack update? (Y/N):
+~~~
+
+You can answer Y.
+
 ### The real update (parameters)
 
 Now lets update the stack by modifying the paramters of the running stack. We will change the flavor of the instance
-which will result in the resource being replaced within the stack. Run the update command but do not provide any
-flags:
+which will result in the resource being replaced within the stack. Run the update command but do not provide the `--defaults` flag:
 
 ~~~
-$ sfn update sparkle-guide-compute
+$ sfn update sparkle-guide-compute --file compute
 ~~~
 
 Now `sfn` will prompt for parameter values. Notice that the default values are the values used when creating the

data/sparkle-guides.gemspec

@@ -1,6 +1,6 @@
 Gem::Specification.new do |s|
   s.name = 'sparkle-guides'
-  s.version = '0.1.4'
+  s.version = '0.1.6'
   s.summary = 'SparkleFormation Guides'
   s.author = 'Chris Roberts'
   s.email = 'chrisroberts.code@gmail.com'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: sparkle-guides
 version: !ruby/object:Gem::Version
-  version: 0.1.4
+  version: 0.1.6
 platform: ruby
 authors:
 - Chris Roberts
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-03-24 00:00:00.000000000 Z
+date: 2016-04-20 00:00:00.000000000 Z
 dependencies: []
 description: SparkleFormation Usage Guides
 email: chrisroberts.code@gmail.com