cfhighlander 0.6.0.alpha.1537959335 → 0.6.0.alpha.1538010880

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fa909a400b28d828b6dfecf42d91e8dd2ff6e04fe546cb9b22a36393d4a264a8
-  data.tar.gz: d5f7bcf65a4a921abf635fcba3a37c4daed684a5c65a09d7f704cae44f9f3850
+  metadata.gz: a1ca60058a558ba23ed08273fa7ec940794476f1fc9228d6077da3521c6d7b19
+  data.tar.gz: 83b85f5799b9d48263174b5adc2ec5db6a6fde698a21e1b0698c36c1a4091ff7
 SHA512:
-  metadata.gz: 35225364f2fc158a4909a737c9426ddf5dc04dd53b54e36eb702258970434450aec27af1519ee8609bc9cb2c216794dc77245a7845e26d61d36da04043a55880
-  data.tar.gz: 56a82fcf00bbf3454dc798749fd8b5a87c89c08423d435bd0c3889c81b9b0244958bb18d462b4fed544640b99b7b981f6cb88b37165e07964567452525ca3c83
+  metadata.gz: 682f0fb7fe00e2ecb5315ec1d5e599591d8a9a8721d55bc40d96fdafbf0fbfadc227b2272aaf20c19802d27fde22c1215a2ef10987fdefb306d42c8ec65ccfe3
+  data.tar.gz: 553b3e35fe13a125bf633da11486167f4946a5f7ea5cc51be92b9189ffb95ef4d614446e191fbbd5b7648952739337419435858b467cc54efd68c7e72939288d

data/README.md

@@ -99,32 +99,48 @@ $ cat out/yaml/application.compiled.yaml | grep  -A3 SubnetCompute0
 
 
 
-# Library
+# Component library
 
-As part of [theonestack org](https://github.com/theonestack/), there is several publicly available components.
+As part of [theonestack org](https://github.com/theonestack/), there are many publicly available components.
 
 - [vpc](https://github.com/theonestack/hl-component-vpc) - Has separation of public
    and private subnets, configurable number of NAT Gateways (per AZ or single for all
-  subnets, handles all of the complex routing stuff)
+  subnets), lays out default subnets (private - compute, storage and cache, public), as well as their route tables
 
 - [ecs](https://github.com/theonestack/hl-component-ecs) - ECS Cluster deployed in VPC Compute Subnets
-- [bastion](https://github.com/theonestack/hl-component-bastion) - Deployed into VPC Public
+- [bastion](https://github.com/theonestack/hl-component-bastion) - Deployed into VPC Public subnets
   Subnets, with configuration for whitelisting IP addresses to access port 22
 - [ecs-service](https://github.com/theonestack/hl-component-ecs-service) - Deploy containerised apps running on ECS Clusters
-- [loadbalancer](https://github.com/theonestack/hl-component-loadbalancer)
+- [loadbalancer](https://github.com/theonestack/hl-component-loadbalancer) - ALB, ELB or NLB
 - [sns](https://github.com/theonestack/hl-component-sns) - SNS Topics, with implemented
 Lambda function to post Slack messages
 - [efs](https://github.com/theonestack/hl-component-efs) - Elastic File System, can be
 used in conjuction with ECS Cluster
+- [rds-mysql](https://github.com/theonestack/hl-component-rds-mysql) - RDS Component for MySQL engine
+- [rds-postgres](https://github.com/theonestack/hl-component-rds-postgres) - RDS Component for Postgres engine
+- [aurora-mysql](https://github.com/theonestack/hl-component-aurora-mysql) - Aurora component for MySQL engine
+- [aurora-postgres](https://github.com/theonestack/hl-component-aurora-postgres) - Aurora component for Postgres engine
+- [elasticache-memcache](https://github.com/theonestack/hl-component-elasticache-memcache) - Aws Elasticache - Memcache engine 
+- [elasticache-memcache](https://github.com/theonestack/hl-component-elasticache-redis) - Aws Elasticache - Redis engine 
+- [asg](https://github.com/theonestack/hl-component-asg) - AutoScalingGroup component
+- [cognito](https://github.com/theonestack/hl-component-cognito) - Cognito user pools, custom domain names and clients
 
 You can easily test any of these. Automatic component resolver will default
 to 'https://github.com/theonestack/hl-component-$name' location if component
 is not found in local sources.
 
-```
-cfcompile [componentname]
+From shell, command below will generate cloudformation for given component in `out` folder
+```shell
+cfcompile component_name
 ```
 
+Or from outer cfhighlander template, just pull component using `Component` DSL statement 
+
+```ruby
+CfhighlanderTemplate do
+  Component component_name
+end
+```
 
 
 # How it works ?
@@ -694,6 +710,16 @@ $ cfhighlander cfcompile [component] [-v distributedversion]
 
 ## Global Extensions
 
-Any extensions placed within `cfndsl_ext` folder will be
-available in cfndsl templates of all components. Any extensions placed within `hl_ext` folder are
+Any extensions placed within `cfndsl_ext` folder in core library code are
+available in cfndsl templates of all components. Any extensions placed within `hl_ext` in core library code are
 available in cfhighlander templates of all components.
+
+
+## Environment variables
+
+`CFHIGHLANDER_WORKDIR` - defaults to $PWD, determines location of 'out' folder where all of the
+generated files are placed
+
+`CFHIGHLANDER_AWS_RETRY_LIMIT` - defaults to 10. Number of retries for AWS SDK before giving up. 
+AWS SDK uses exponential backoff to make the API calls
+ 

data/bin/cfhighlander.rb

@@ -9,6 +9,7 @@
 
 require 'thor'
 require 'rubygems'
+require 'aws-sdk-core'
 require_relative '../lib/cfhighlander.compiler'
 require_relative '../lib/cfhighlander.factory'
 require_relative '../lib/cfhighlander.publisher'
@@ -180,4 +181,6 @@ if ENV['HIGHLANDER_WORKDIR'].nil?
   ENV['HIGHLANDER_WORKDIR'] = Dir.pwd
 end
 
+Aws.config[:retry_limit]= if ENV.key? 'CFHIGHLANDER_AWS_RETRY_LIMIT' then (ENV['CFHIGHLANDER_AWS_RETRY_LIMIT'].to_i) else 10 end
+
 HighlanderCli.start

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cfhighlander
 version: !ruby/object:Gem::Version
-  version: 0.6.0.alpha.1537959335
+  version: 0.6.0.alpha.1538010880
 platform: ruby
 authors:
 - Nikola Tosic
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-09-26 00:00:00.000000000 Z
+date: 2018-09-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: highline