initial commit

Author: brandonjbjelland

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,21 @@
+# I have issues
+
+## I'm submitting a
+
+* [ ] bug report
+* [ ] feature request
+* [ ] support request
+
+## What is the current behavior
+
+## If this is a bug, how to reproduce? Please include a code sample
+
+## What's the expected behavior
+
+## Environment
+
+* Affected module version:
+* OS:
+* Terraform version:
+
+## Other relevant info

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+# PR o'clock
+
+## Description
+
+Please explain the changes you made here and link to any relevant issues.
+
+### Checklist
+
+- [ ] `terraform fmt` and `terraform validate` both work from the root and `examples/ebs_optimized_test_fixture` directories (look in CI for an example)
+- [ ] Tests for the changes have been added and passing (for bug fixes/features)
+- [ ] Test results are pasted in this PR (in lieu of CI)
+- [ ] Docs have been added/updated (for bug fixes/features)
+- [ ] Any breaking changes are noted in the description above

.gitignore

@@ -0,0 +1,9 @@
+*.tfvars
+*.tfstate*
+.terraform/
+**/inspec.lock
+*.gem
+.kitchen/
+.kitchen.local.yml
+Gemfile.lock
+terraform.tfstate.d/

.kitchen.yml

@@ -0,0 +1,30 @@
+---
+driver:
+  name: terraform
+  root_module_directory: examples/ebs_optimized_test_fixture
+
+provisioner:
+  name: terraform
+
+platforms:
+- name: aws
+
+verifier:
+  name: terraform
+
+suites:
+  -
+    name: default
+    verifier:
+      groups:
+        -
+          name: default
+          attributes:
+            supported: supported
+            unsupported: unsupported
+            unknown_type_result: unknown
+            ebs_optimized_instance_id: ebs_optimized_instance_id
+            not_ebs_optimized_instance_id: not_ebs_optimized_instance_id
+          controls:
+            - ebs_optimized
+

.pre-commit-config.yaml

@@ -0,0 +1,16 @@
+# See http://pre-commit.com for more information
+# See http://pre-commit.com/hooks.html for more hooks
+repos:
+- repo: git://github.com/antonbabenko/pre-commit-terraform
+  rev: v1.7.1
+  hooks:
+    - id: terraform_fmt
+    # - id: terraform_docs
+- repo: git://github.com/pre-commit/pre-commit-hooks
+  rev: v1.2.3
+  hooks:
+    - id: check-merge-conflict
+    -   id: trailing-whitespace
+    # -   id: end-of-file-fixer
+    -   id: check-yaml
+    -   id: check-added-large-files

.rspec

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

.ruby-version

@@ -0,0 +1 @@
+2.4.2

.travis.yml

@@ -0,0 +1,50 @@
+language: ruby
+sudo: required
+dist: trusty
+
+services:
+- docker
+
+rvm:
+- 2.4.2
+
+before_install:
+- echo "before_install"
+
+install:
+- echo "install"
+- gem install bundler --no-rdoc --no-ri
+- bundle install
+
+before_script:
+- echo 'before_script'
+- export AWS_REGION='us-east-1'
+- export TF_VAR_region=${AWS_REGION}
+- echo "using AWS_REGION=${AWS_REGION}"
+- export TF_WARN_OUTPUT_ERRORS=1
+- curl --silent --output terraform.zip https://releases.hashicorp.com/terraform/0.11.7/terraform_0.11.7_linux_amd64.zip
+- sha256sum terraform.zip  | grep "6b8ce67647a59b2a3f70199c304abca0ddec0e49fd060944c26f666298e23418"
+- unzip terraform.zip ; rm -f terraform.zip; chmod +x terraform
+- mkdir -p ${HOME}/bin ; export PATH=${PATH}:${HOME}/bin; mv terraform ${HOME}/bin/
+- terraform -v
+
+script:
+- echo 'script'
+- terraform init
+- terraform fmt -check=true
+- terraform validate -var "region=${AWS_REGION}" -var "instance_type=t2.micro"
+- docker run --rm -v $(pwd):/app/ --workdir=/app/ -t wata727/tflint --error-with-issues
+- cd examples/ebs_optimized_test_fixture
+- terraform init
+- terraform fmt -check=true
+- terraform validate
+- cd -
+- terraform -v
+- bundle exec kitchen test --destroy always
+
+notifications:
+  email:
+    recipients:
+    - brandon@atscale.run
+    on_success: change
+    on_failure: change

CHANGELOG.md

@@ -0,0 +1,12 @@
+# Change Log
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/) and this
+project adheres to [Semantic Versioning](http://semver.org/).
+
+## [v0.1.0] - 2018-06-08
+
+### Added
+
+- Everything! Initial release of the module.

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# 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 brandon@atscale.run. The project team will review and investigate all complaints, and will respond in a way that it deems 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/