auster 0.2.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 53c4b1f54eb6c85806e15fd5d0c10d084237143c
+  data.tar.gz: 8fc7812b3c331168454559e81780a390214b1ff0
+SHA512:
+  metadata.gz: 74bcbed24f715040cabe0063e56a77f8beeeedd8d3223a3480d2507ffa7f28e35014fb85681f64e169de51993802b91e9d8c92850a463363b98da38bab4ccc12
+  data.tar.gz: 229f261906b6843db306c25a569f9dec2324038b2b0dbb638f04254f7e89199b8644d3b6af02c52d9493aba2692aec3be66b914cf09fbc9b43e6791798be5ff0

data/.editorconfig

@@ -0,0 +1,13 @@
+[*]
+insert_final_newline = true
+charset = utf-8
+
+[*.md]
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = true
+
+[*.{js,json,rb}]
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = true

data/.gitignore

@@ -0,0 +1,9 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/.rubocop.yml

@@ -0,0 +1,41 @@
+AllCops:
+  TargetRubyVersion: 2.3
+  Exclude:
+    - "*.gemspec"
+
+Metrics/AbcSize:
+  Enabled: false # because ABC tells you nothing useful!
+
+Metrics/LineLength:
+  Max: 120
+
+Metrics/BlockLength:
+  Exclude:
+    - "Rakefile"
+    - "spec/**/*.rb"
+
+Metrics/ClassLength:
+  Max: 1500
+  
+Metrics/MethodLength:
+  Max: 35
+
+Metrics/ModuleLength:
+  Max: 1500
+  Exclude:
+    - "spec/**/*.rb"
+
+Metrics/ParameterLists:
+  Enabled: false # this is a really strange thing when you use named parameters.
+
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+
+Style/Documentation:
+  Enabled: false
+
+Style/DoubleNegation:
+  Enabled: false # avoids dangling object pointers
+
+Performance/RedundantBlockCall:
+  Enabled: false # because `block.call` is more explicit than a "yield" somewhere down low

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.3.0
+before_install: gem install bundler -v 1.13.6

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at ed@edropple.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gemspec

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 Ed Ropple
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,152 @@
+# Auster #
+_The Best Way To Wrangle CloudFormation (at least, according to me!)_
+
+**Auster** is a best-practices extension to the [Cfer](https://github.com/seanedwards/cfer) environment that establishes conventions for effectively working with Cfer and CloudFormation. It's developed from some of the lessons that I've learned over time building out large-scale systems for companies big and small and running into the stumbling blocks that always pop up when trying to automate a full stack deployment.
+
+The biggest roadblock to making your deployment awesome is the impedance mismatch between tools like CloudFormation (and implicitly Cfer) and the world you're working in. CloudFormation is a declarative system: "this should exist when you're done". And that's great...until you have to start introducing stateful changes to your system! (Which, if you're doing it right, will be approximately "five seconds after you stand up an RDS server.") This is where Auster comes in, allowing you to orchestrate those stateful transitions between steps.
+
+**Caveat emptor:** The code that became Auster has been in use for a few months, but Auster itself is very much a work in progress. I use this for stuff that pays money and I'll stand behind it, but you should make your own call.
+
+## Give It A Try ##
+Auster is installable via Rubygems (`gem install auster`), but the example repo is in the same repository, so checking it out is recommended.
+
+```bash
+$ gem install auster
+$ git clone git@github.com:eropple/auster.git
+$ cd auster/example-repo
+```
+
+Take a look around the repo if you'd like. Ensure that you have valid AWS credentials in your environment (`AWS_PROFILE`, etc.) and then run the following to create a pair of CloudFormation stacks. All they'll do is create S3 buckets, so you won't be charged for anything.
+
+```bash
+$ auster run us-west-2/dev-ed1 bootstrap
+$ auster run us-west-2/dev-ed1 dependent
+```
+
+If you read through the Auster output, you'll see that it's creating S3 buckets (as you'd expect--it's still CloudFormation under the hood) and registering them as region-wide exports, prefixed with the plan ID `dev1-ed`.
+
+Anyhoo, let's clean up.
+
+```bash
+$ auster nuke us-west-2/dev-ed1
+```
+
+If you'd like more information on writing Cfer itself, check out [chef-cfer-consul-cluster](https://github.com/seanedwards/chef-cfer-consul-cluster).
+
+## Auster Commands ##
+### Generators ###
+- `auster generate repo` - Creates a Auster plan repo with sample files.
+- `auster generate step ##.human-tag` - Creates a new Auster step with stub files.
+
+### Executors ###
+**Note:** In the command line interface, the step number and the tag are interchangeable. `auster run region/env 00` and `auster run region/env human-tag` will refer to the same step, `00.human-tag`.
+
+- `auster json us-west-2/dev1-ed (##|human-tag)` - Uses `cfer generate` to generate the output JSON that will be applied when this step is `auster run`'d.
+- `auster run us-west-2/dev1-ed (##|human-tag)` - Runs step 01 in region `us-west2` with configuration set `dev1-ed`. This will:
+  - If `/cfg/_schema.yaml` exists, it will validate `/cfg/us-west2/dev1-ed.yaml` against it and fail if it does not validate.
+  - If this is the first run of this step (there is no `dev1-ed-step01` CloudFormation stack in AWS), the scripts in `/steps/01/on-create.d` will be run in lexicographic order.
+  - The scripts in `/steps/01/pre-converge.d` will be run in lexicographic order.
+  - Cfer will be run against the scripts in `/steps/01/cfer` to generate and apply the desired CloudFormation template.
+  - The scripts in `/steps/01/post-converge.d` will be run in lexicographic order.
+- `auster destroy us-west-2/dev1-ed (##|human-tag)` - Destroys step 01 in region `us-west2` with configuration set `dev1-ed`. This will:
+  - Attempt to destroy the CloudFormation stack `dev1-ed-step01`. _This is not guaranteed to succeed_, especially if this stack has exports being used by other stacks.
+  - If the stack is destroyed successfully, the scripts in `/steps/01/on-destroy.d` will be run in lexicographic order.
+- `auster nuke us-west-2/dev1-ed` - Destroys _all_ steps in `dev1-ed` in region `us-west2`. This will request a confirmation (and will error out if no TTY is detected); you must pass the `--force` parameter to automate this destruction.
+
+## Auster Config Sets ##
+A _config set_ is a YAML file that combines Cfer parameters and Auster directives. This file may optionally be proofed with a Kwalify YAML schema in `/config/schema.yaml` and, once loaded, the loaded parameters can be proofed via a `Cfer::Auster::ParamValidator` specified in `/config/validator.rb`.
+
+All Auster-specific parameters are stored under the `AusterOptions` key.
+
+- `AusterOptions`
+  - `S3Path`: Specifies an S3 path at which to upload the CloudFormation stack template. (This is required once your stack definition grows over a certain size; I recommend you always use it.) For Cfer uses, this is both `--s3-path` and `--force-s3`.
+
+## Auster Event Scripts ##
+There are four events for every step at which arbitrary scripts can be run: `on-create`, `pre-converge`, `post-converge`, and  `on-destroy`. (Yes, that the lexicographic ordering of `post` comes before `pre` drives me up the wall too. Sorry.) Every script in the appropriate directory within each step will be executed (based on chmod status via `File::executable?`). Ruby scripts will be loaded in-process and run directly, while all other scripts will be invoked via `system()` (so on Unixes the shebang will be evaluated, etc.).
+
+Some folks have asked why we have `pre-converge` and `post-converge` steps. The reason for this is because occasionally your cloud stack is going to require manual intervention. But you might want to react to that manual intervention before starting the next step--so you can prompt your operator to perform their manual task in Step X's `post-converge` and react to it in Step X+1's `pre-converge`.
+
+While this gem _should_ in all cases be Windows-compatible, event scripts are the most likely place to run into jank. Your PowerShell and batch scripts _should_ work but this is not guaranteed. Bug reports and pull requests welcome. Obviously, running those scripts in a cross-platform way is a total no-go, so if you need to run in a cross-platform environment you should stick to writing your scripts in Ruby.
+
+**Important:** `pre-converge` and `post-converge` _will_ run even if there are no changes applied to CloudFormation resources. This makes Auster a handy place to do stuff like rolling database credentials.
+
+### Environment Variables in Event Scripts ###
+- `PLAN_ID`: the identifier of this Auster stack, i.e., for `us-west-2/dev-ed1` `PLAN_ID` would equal `dev-ed1`.
+- `AWS_REGION`/`AWS_DEFAULT_REGION`: the AWS region of this Auster stack
+
+### Ruby Methods in Event Scripts ###
+- `plan_id`: the identifier of this Auster stack, as per `PLAN_ID`.
+- `aws_region`: the AWS region of this Auster stack, as per `AWS_REGION`.
+- `repo`: the `Cfer::Auster::Repo` object representing the entire repo.
+- `config_set`: the `Cfer::Auster:Config` object representing the collection of parameters related to this environment.
+- `exports(export_plan_id = PLAN_ID)`: fetches all CloudFormation exports for a given plan (by default, the one of the secuting stack). The preferred method of accessing data from a dependent stack.
+- `repo.step_by_tag(tag).cfn_data(config_set)`: retrieves all parameters and outputs of a given step and environment.
+
+## Auster Cfer Scripts ##
+**Note:** Auster wraps Cfer at an API level rather than at a command-line level, so feature parity is an ongoing process. In particular, stack policies are not currently supported--it's a mix of not having a Ruby DSL for them and not having a direct need for them myself at the moment. Pull requests welcome!
+
+Auster uses a convention-based arrangement for structuring the Cfer scripts that will be processed into CloudFormation. The order of evaluation is as follows:
+
+- `/cfer-helpers/**/*.rb` - global-scope helpers.
+- `/steps/##.tag/cfer/helpers/**/*.rb` - script-scope helpers.
+- `/steps/##.tag/cfer/require.rb` - intended for checking preconditions, requiring libraries used downstream (my favorite is `ipaddress`!), etc.
+- `/steps/##.tag/cfer/parameters.rb` - intended for defining `parameter`s.
+- `/steps/##.tag/cfer/exports.rb` - intended for defining `output`s and `export`s.
+- `/steps/##.tag/cfer/defs/**/*.rb` - intended for defining `resource`s.
+
+### Auster Cfer Helpers ###
+- `import_value(name)`: Wrapper around `Fn::ImportValue` that prepends the current plan's ID to the name in question.
+- `export(name, value)`: Wrapper around `output` to export the value in question. Prepends the plan's ID in the same way that `import_value` expects.
+
+## Structure ##
+Each Auster plan is laid out as per the following directory structure:
+
+- `/`
+  - `/.auster.yaml` - Currently empty; intended for future global configuration. (Necessary to find the base of a repo, a la Rakefile/Gemfiles.)
+  - `/Gemfile` - Used for script dependencies, etc. as per usual. (You should probably require `auster` here too, to version-pin it.)
+  - `/config`
+    - `/schema.yaml` - (optional) a [Kwalify](http://www.kuwata-lab.com/kwalify/ruby/users-guide.html) schema against which a configuration file will be checked before any operations can be taken.
+    - `/validator.rb` - (optional) a `Cfer::Auster::ParamValidator` that, if it exists, will be run against the parameter set _after_ YAML loading but _before_ Cfer is run.
+    - `/us-west-2` - the AWS region for this configuration set. (This value is not typechecked.)
+      - `/dev1-ed.yaml` - a YAML file that will be surfaced as Cfer parameters
+        - The basename (filename sans extension) must begin with an alphabetic character and may only contain alphanumerics (case sensitive) and numbers. It must be under 16 characters in length.
+        - The filename sans extension will be used as an identifier for steps executed with its configuration, i.e. the CloudFormation stack for `dev1-ed` will be called `dev1-ed-step00` and exports from a step in `dev1-ed` will be called `dev1-ed-YourExportName`.
+          - This identifier is exposed in your Cfer scripts as `parameters[:AusterID]`.
+        - This parameter set will be checked into source control and so should have _no_ secrets in it! This is for configuration parameters like:
+          - VPC CIDR block allocation
+          - Autoscaling group sizes
+          - Instance sizes
+          - Domain names (for feeding into Route 53)
+        - The AWS region of this stack is exposed in your Cfer scripts as `parameters[:AWSRegion]`.
+  - `/cfer-helpers`
+    - A set of Ruby files that are included into every Cfer scope. Intended for global-scope helper methods.
+  - `/steps`
+    - `/00.human-tag`
+      - `/cfer`
+        - `/defs`
+          - A set of Ruby files containing Cfer `resource` declarations. These will be evaluated in lexicographic order, but should not be reliant on behaviors in any other file!
+        - `helpers`
+          - A set of Ruby files that will be included into the Cfer scope. Intended for script-specific helper methods.
+        - `/parameters.rb` - Cfer `parameter` invocations and `Auster.import` calls (which will be automatically prepended with the stack name).
+        - `/outputs.rb` - Cfer `output` invocations and `Auster.export` calls (which will be automatically prepended with the stack name).
+        - `/require.rb` - every other Cfer file will be executed in the context of `require.rb`. This is not guaranteed to be executed only once and so no stateful changes should be made here.
+      - `/on-create.d`
+        - A set of scripts to be run when the step is first executed.
+      - `/on-destroy.d`
+        - A set of scripts to be run when the Cfer stack is being torn down.
+      - `/pre-converge.d`
+        - A set of scripts to be run at the start of the Cfer run.
+      - `/post-converge.d`
+        - A set of scripts to be run at the successful end of the Cfer run.
+    - `/01.human-tag`
+      - ...
+    - `/02.human-tag`
+      - ...
+
+## Contributing ##
+Bug reports and pull requests are welcome on GitHub at https://github.com/eropple/cfer-auster. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. (And I mean it.)
+
+
+## License ##
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
+

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/auster.gemspec

@@ -0,0 +1,37 @@
+# coding: utf-8
+# frozen_string_literal: true
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "cfer/auster/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "auster"
+  spec.version       = Cfer::Auster::VERSION
+  spec.authors       = ["Ed Ropple"]
+  spec.email         = ["ed+auster@edropple.com"]
+
+  spec.summary       = "Best-practices tooling for CloudFormation and AWS."
+  spec.homepage      = "https://github.com/eropple/auster"
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files -z`.split("\x0").reject do |f|
+    f.match(%r{^(test|spec|features)/})
+  end
+  spec.bindir        = "bin"
+  spec.executables   = ["auster"]
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.13"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rspec", "~> 3.0"
+  spec.add_development_dependency "pry"
+
+  spec.add_runtime_dependency "cri", "~> 2.8.0"
+  spec.add_runtime_dependency "search_up", "~> 1.0.2"
+  spec.add_runtime_dependency "activesupport", "~> 5.0.2"
+  spec.add_runtime_dependency "ice_nine", "~> 0.11.2"
+  spec.add_runtime_dependency "kwalify", "~> 0.7.2"
+  spec.add_runtime_dependency "cfer", "~> 0.5.0"
+  spec.add_runtime_dependency "semantic", "~> 1.6.0"
+  spec.add_runtime_dependency "aws-sdk", "~> 2.9.11"
+end

data/bin/auster

@@ -0,0 +1,8 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+lib = File.expand_path("../lib", __dir__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+
+require "cfer/auster/cli"
+
+Cfer::Auster::CLI.execute(ARGV)

data/bin/console

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "bundler/setup"
+require "cfer/auster"
+
+require "pry"
+Pry.start

data/example-repo/config/schema.yaml

@@ -0,0 +1,10 @@
+type: map
+mapping:
+  Foo: { type: int, required: yes }
+  Bar: { type: scalar, required: no }
+  Baz:
+    type: map
+    mapping:
+      Something: { type: bool, required: yes }
+      Else: { type: bool, required: no }
+      Okay: { type: scalar, required: yes }

data/example-repo/config/us-west-2/dev-ed1.yaml

@@ -0,0 +1,7 @@
+Foo: 1
+Bar: ~
+
+Baz:
+  Something: yes
+  Else: no
+  Okay: sure

data/example-repo/config/validator.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+Cfer::Auster::ParamValidator.new do |parameters, errors|
+  errors << "nope" if parameters.nil?
+end

data/example-repo/steps/00.bootstrap/cfer/defs/s3.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+resource :TempBucket, "AWS::S3::Bucket" do; end

data/example-repo/steps/00.bootstrap/cfer/outputs.rb

@@ -0,0 +1 @@
+export :TempBucket1, Fn.ref(:TempBucket)

data/example-repo/steps/00.bootstrap/on-create.d/00-debug.rb

@@ -0,0 +1,4 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+
+logger.info "!! step 00, on-create"

data/example-repo/steps/00.bootstrap/on-destroy.d/00-debug.rb

@@ -0,0 +1,4 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+
+logger.info "!! step 00, on-destroy"

data/example-repo/steps/00.bootstrap/post-converge.d/00-debug.rb

@@ -0,0 +1,5 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+
+logger.info "!! step 00, post-converge"
+logger.info "Exported TempBucket1: #{exports[:TempBucket1]}"

data/example-repo/steps/00.bootstrap/pre-converge.d/00-debug.rb

@@ -0,0 +1,4 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+
+logger.info "!! step 00, pre-converge"

data/example-repo/steps/01.dependent/cfer/defs/s3.rb

@@ -0,0 +1,3 @@
+# frozen_string_literal: true
+
+resource :TempBucket, "AWS::S3::Bucket" do; end

data/example-repo/steps/01.dependent/cfer/outputs.rb

@@ -0,0 +1 @@
+export :TempBucket2, import(:TempBucket1)

data/example-repo/steps/01.dependent/on-create.d/00-debug.rb

@@ -0,0 +1,4 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+
+logger.info "!! step 01, on-create"

data/example-repo/steps/01.dependent/on-destroy.d/00-debug.rb

@@ -0,0 +1,4 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+
+logger.info "!! step 01, on-destroy"

data/example-repo/steps/01.dependent/post-converge.d/00-debug.rb

@@ -0,0 +1,7 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+
+logger.info "!! step 01, post-converge"
+logger.info exports.inspect
+logger.info "Exported TempBucket1: #{exports[:TempBucket1]}"
+logger.info "Exported TempBucket2: #{exports[:TempBucket2]}"

data/example-repo/steps/01.dependent/pre-converge.d/00-debug.rb

@@ -0,0 +1,5 @@
+#! /usr/bin/env ruby
+# frozen_string_literal: true
+
+logger.info "!! step 01, pre-converge"
+logger.info "Exported TempBucket1: #{exports[:TempBucket1]}"