tfctl 1.0.0.rc1 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7851ad9d647739e471f8d430dace8564f16f403f3a7e7ffb98e21384db641f53
-  data.tar.gz: d52713addc4006e2e67f5c3fce56941697d4a9edfb6bea08953c76eeb673c2f1
+  metadata.gz: 6d47682cf9949db840c18d07b6f06907a9d36e2a75d0a5255b4c57f3603c0dbf
+  data.tar.gz: d5a81e877943fff53e903a104249e1147a827c593430bc91c0b78d5cc467fc4b
 SHA512:
-  metadata.gz: 10f6a9bce18e905d787783a6f61a3f93724b4809d1c7f2c7e7c1edc155ba2c14b17a97096140f790c9b7e250dc4fd24f7af5c86fefea8139d25e1b15dddc65d3
-  data.tar.gz: 9e81ab6abbc15df5917ea6b23a1b167a2cd745e057d462ce0e28db47b27c6f12477c62293893c59f1977c5c406df31dbb797818fc27978b5bd9255a12bd86370
+  metadata.gz: 03b7d69b7a7bbf296b0b1ab3aa8794d8b91e51559a1e2ee1d450396615aeba495b63993f84866c6fe5997d34c760da143cb66ca0cabc2a1a5a1266b701676bac
+  data.tar.gz: f9ebdae72fd58473c3a8cc5015fd2d2e32092488218b52efa79e2d625802ccdf4447298e45497d4ec0e03583b0edbd3a31b51e92f76a5981a5f3819f9cee1e4a

data/CHANGELOG.adoc

@@ -1,6 +1,6 @@
 = Changelog
 
-== 1.0.0-rc1 (unreleased)
+== 1.0.0
 
 * feat(config): JSON schema config validation
 * feat(config): added 'data' parameter

data/docs/configuration.adoc

@@ -1,4 +1,28 @@
-== Configuration
+// Settings:
+:idprefix:
+:idseparator: -
+ifndef::env-github[:icons: font]
+ifdef::env-github,env-browser[]
+:toc: macro
+:toclevels: 1
+endif::[]
+ifdef::env-github[]
+:branch: master
+:status:
+:outfilesuffix: .adoc
+:!toc-title:
+:caution-caption: :fire:
+:important-caption: :exclamation:
+:note-caption: :paperclip:
+:tip-caption: :bulb:
+:warning-caption: :warning:
+endif::[]
+
+= Configuration
+
+toc::[]
+
+== Overview
 
 Tfctl retrieves initial account configuration from AWS Organizations and merges
 it with configuration specified in a yaml file.
@@ -48,7 +72,7 @@ TIP: You can display the fully merged configuration by running `tfctl -c
 conf/CONFIG_FILE.yaml -s`.  It's safe to run as it doesn't make any changes to
 AWS resources.  It's a good way to test your configuration.
 
-=== Defining arbitrary data
+== Defining arbitrary data
 
 You can define arbitrary data under the `data:` parameter, both in the root of
 the config and in the organization sections.  It will be available in Terraform
@@ -57,7 +81,7 @@ subnet ranges, s3 bucket names and so on.  `data:` in organization sections
 will be merged with accounts following the usual merge order as described
 above.
 
-=== Handling secrets
+== Handling secrets
 
 No secrets should be committed into Terraform or tfctl configuration.  Use AWS
 Secrets Manager instead and retrieve in Terraform profiles using

data/docs/control_tower.adoc

@@ -1,12 +1,32 @@
-:toc:
-
-== Control Tower integration guide
+// Settings:
+:idprefix:
+:idseparator: -
+ifndef::env-github[:icons: font]
+ifdef::env-github,env-browser[]
+:toc: macro
+:toclevels: 1
+endif::[]
+ifdef::env-github[]
+:branch: master
+:status:
+:outfilesuffix: .adoc
+:!toc-title:
+:caution-caption: :fire:
+:important-caption: :exclamation:
+:note-caption: :paperclip:
+:tip-caption: :bulb:
+:warning-caption: :warning:
+endif::[]
+
+= Control Tower integration guide
 
 This guide will help you integrate Terraform with AWS Control Tower using the
 tfctl wrapper.  This involves setting up resources for remote state tracking,
 necessary IAM roles and a tfctl project.
 
-=== Overview
+toc::[]
+
+== Overview
 
 For state tracking we're going to create a dedicated `shared-services` account
 under a `mgmt` organization unit.  We'll use S3 for state storage and DynamoDB
@@ -26,7 +46,7 @@ account factory and can be assumed from the primary account.
 We're going to create a `live` and `test` organization units in Control Tower
 and provision a couple of accounts for testing.
 
-=== Prerequisites
+== Prerequisites
 
 Before starting you'll need:
 
@@ -35,7 +55,7 @@ Before starting you'll need:
  * AWS CLI tools installed on your machine.
  * Terraform 0.12 or higher.
 
-=== Configure Control Tower
+== Configure Control Tower
 
 Create the following organization units in Control Tower:
 
@@ -52,14 +72,14 @@ Then provision accounts:
 NOTE: Control Tower accounts need to be provisioned one at a time.  It takes
 approximately 20 mins to provision one.
 
-=== Install tfctl
+== Install tfctl
 
 ----
 git clone git@github.com:scalefactory/tfctl.git
 cd tfctl/ && sudo make install
 ----
 
-=== Set up AWS resources
+== Set up AWS resources
 
 It's assumed you have configured AWS CLI access to the primary account.
 
@@ -128,7 +148,7 @@ aws cloudformation describe-stacks --stack-name TfctlOrgAccess
 
 NOTE: Successful status should read: `CREATE_COMPLETE`.
 
-=== Configure tfctl
+== Configure tfctl
 
 Copy the example project directory `examples/control_tower` somewhere convenient
 and edit `conf/example.yaml`.
@@ -142,7 +162,7 @@ You need to modify the following parameters:
 
 TIP: You should keep your project directory under version control.
 
-=== Deploy example tfctl profile
+== Deploy example tfctl profile
 
 The example profile will create an S3 bucket in accounts under `test`, `live`
 and `mgmt` OUs.

data/docs/creating_a_profile.adoc

@@ -1,9 +1,31 @@
-== Creating and deploying a tfctl profile
+// Settings:
+:idprefix:
+:idseparator: -
+ifndef::env-github[:icons: font]
+ifdef::env-github,env-browser[]
+:toc: macro
+:toclevels: 1
+endif::[]
+ifdef::env-github[]
+:branch: master
+:status:
+:outfilesuffix: .adoc
+:!toc-title:
+:caution-caption: :fire:
+:important-caption: :exclamation:
+:note-caption: :paperclip:
+:tip-caption: :bulb:
+:warning-caption: :warning:
+endif::[]
+
+= Creating and deploying a tfctl profile
 
 This guide will show you how to create a tfctl profile, declare some resources
 in it and deploy it to to a group of accounts in an organization unit.
 
-=== Create a new profile
+toc::[]
+
+== Create a new profile
 
 In your tfctl project directory create a new profile:
 
@@ -87,7 +109,7 @@ resource "aws_s3_bucket" "example" {
 This will create an S3 bucket with a name containing the current account name
 (which will vary depending on which account it's deployed to).
 
-=== Assign profile to accounts
+== Assign profile to accounts
 
 Before you can deploy the new profile you need to tell `tfctl` which accounts
 to deploy it to.
@@ -113,7 +135,7 @@ organization_units:
 ----
 
 
-=== Plan
+== Plan
 
 To see what would happen when the change is applied run:
 
@@ -161,7 +183,7 @@ what went wrong.
 tfctl will generate a plan file automatically and use it with `apply` in the
 next step.
 
-=== Apply
+== Apply
 
 Once you're happy with the plan, apply it.
 ----

data/docs/iam_permissions.adoc

@@ -1,4 +1,24 @@
-== IAM roles
+// Settings:
+:idprefix:
+:idseparator: -
+ifndef::env-github[:icons: font]
+ifdef::env-github,env-browser[]
+:toc: macro
+:toclevels: 1
+endif::[]
+ifdef::env-github[]
+:branch: master
+:status:
+:outfilesuffix: .adoc
+:!toc-title:
+:caution-caption: :fire:
+:important-caption: :exclamation:
+:note-caption: :paperclip:
+:tip-caption: :bulb:
+:warning-caption: :warning:
+endif::[]
+
+= IAM roles
 
 Tfctl usually requires three IAM roles to be configured:
 

data/docs/project_layout.adoc

@@ -1,4 +1,24 @@
-== Project layout
+// Settings:
+:idprefix:
+:idseparator: -
+ifndef::env-github[:icons: font]
+ifdef::env-github,env-browser[]
+:toc: macro
+:toclevels: 1
+endif::[]
+ifdef::env-github[]
+:branch: master
+:status:
+:outfilesuffix: .adoc
+:!toc-title:
+:caution-caption: :fire:
+:important-caption: :exclamation:
+:note-caption: :paperclip:
+:tip-caption: :bulb:
+:warning-caption: :warning:
+endif::[]
+
+= Project layout
 
 Example project structure
 ----
@@ -16,7 +36,9 @@ project_dir/
         └── variables.tf
 ----
 
-=== tfctl configuration file
+toc::[]
+
+== tfctl configuration file
 
 Assigns Terraform profiles and configuration to accounts based on:
 
@@ -29,7 +51,7 @@ The configuration data is exposed to terraform via a profile `config` variable.
 It also defines Terraform and tfctl configuration such as state tracking and
 what IAM roles to use.
 
-=== profiles
+== profiles
 
 Profiles are re-usable collections of resources which can be applied to
 accounts.  They are implemented just like usual modules but provide an
@@ -38,6 +60,6 @@ other data sources).  Profiles often compose multiple modules and provide
 configuration data to them.  This approach makes it possible to re-use standard
 modules (e.g. Terraform module registry).
 
-=== modules
+== modules
 
 Standard Terraform modules.

data/lib/tfctl/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Tfctl
-    VERSION = '1.0.0.rc1'
+    VERSION = '1.0.0'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: tfctl
 version: !ruby/object:Gem::Version
-  version: 1.0.0.rc1
+  version: 1.0.0
 platform: ruby
 authors:
 - Andrew Wasilczuk
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-11-10 00:00:00.000000000 Z
+date: 2019-11-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-organizations
@@ -167,9 +167,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
 rubygems_version: 2.7.7