Release: 1.1.0

.gitignore

@@ -131,7 +131,7 @@ mypy-report.xml
 # pyenv
 #   For a library or package, you might want to ignore these files since the code is
 #   intended to run in multiple environments; otherwise, check them in:
-# .python-version
+.python-version
 
 # pipenv
 #   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.

CONTRIBUTING.md

@@ -2,4 +2,4 @@
 
 Thank you for your interest in contributing to the AWS Control Tower Account Factory for Terraform.
 
-At this time, we are not accepting contributions. If contributions are accepted in the future, the AWS Control Tower Account Factory for Terraform is released under the [Apache license](http://aws.amazon.com/apache2.0/) and any code submitted will be released under that license.
+At this time, we are not accepting contributions. If contributions are accepted in the future, the AWS Control Tower Account Factory for Terraform is released under the [Apache license](http://aws.amazon.com/apache2.0/) and any code submitted will be released under that license.

LICENSE

@@ -198,4 +198,4 @@
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
-   limitations under the License.
+   limitations under the License.

README.md

@@ -163,4 +163,4 @@ Now that you have configured and deployed AWS Control Tower Account Factory for
 | <a name="output_terraform_version"></a> [terraform\_version](#output\_terraform\_version) | n/a |
 | <a name="output_tf_backend_secondary_region"></a> [tf\_backend\_secondary\_region](#output\_tf\_backend\_secondary\_region) | n/a |
 | <a name="output_vcs_provider"></a> [vcs\_provider](#output\_vcs\_provider) | n/a |
-<!-- END_TF_DOCS -->
+<!-- END_TF_DOCS -->

VERSION

@@ -1 +1 @@
-1.0.12
+1.1.0

examples/bitbucket+tf_enterprise/main.tf

@@ -18,4 +18,4 @@ module "aft" {
   terraform_api_endpoint = "https://terraform.example.com/api/v2/"
   terraform_token        = "EXAMPLE-uoc1c1qsw7poexampleewjeno1pte3rw"
   terraform_org_name     = "ExampleOrg"
-}
+}

examples/codecommit+tf_oss/main.tf

@@ -7,4 +7,4 @@ module "aft" {
   aft_management_account_id   = "777788889999"
   ct_home_region              = "us-east-1"
   tf_backend_secondary_region = "us-west-2"
-}
+}

examples/github+tf_oss/main.tf

@@ -13,4 +13,4 @@ module "aft" {
   global_customizations_repo_name               = "ExampleOrg/example-repo-2"
   account_customizations_repo_name              = "ExampleOrg/example-repo-3"
   account_provisioning_customizations_repo_name = "ExampleOrg/example-repo-4"
-}
+}

examples/githubenterprise+tf_cloud/main.tf

@@ -18,4 +18,4 @@ module "aft" {
   terraform_distribution = "tfc"
   terraform_token        = "EXAMPLE-uoc1c1qsw7poexampleewjeno1pte3rw"
   terraform_org_name     = "ExampleOrg"
-}
+}

git-secrets/.gitattributes

@@ -0,0 +1,10 @@
+# Set the default behavior, in case people don't have core.autocrlf set.
+* text=auto
+
+# Force the bash scripts to be checked out with LF line endings.
+git-secrets text eol=lf
+git-secrets.1 text eol=lf
+test/bats/bin/* text eol=lf
+test/bats/libexec/* text eol=lf
+*.bats text eol=lf
+*.bash text eol=lf

git-secrets/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,6 @@
+*Issue #, if available:*
+
+*Description of changes:*
+
+
+By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

git-secrets/.pre-commit-hooks.yaml

@@ -0,0 +1,5 @@
+-   id: git-secrets
+    name: Git Secrets
+    description: git-secrets scans commits, commit messages, and --no-ff merges to prevent adding secrets into your git repositories.
+    entry: 'git-secrets --pre_commit_hook'
+    language: script

git-secrets/.travis.yml

@@ -0,0 +1,8 @@
+language: bash
+
+before_install:
+- git config --global user.email "[email protected]"
+- git config --global user.name "Your Name"
+
+script:
+- make test

git-secrets/CHANGELOG.md

@@ -0,0 +1,49 @@
+# CHANGELOG
+
+## 1.3.0 - 2019-02-10
+
+* Empty provider output is now excluded
+  (https://github.com/awslabs/git-secrets/issues/34)
+* Spaces are now supported in git exec path, making more Windows
+  paths execute properly.
+* Patterns with newlines and carriage returns are now loaded properly.
+* Patterns that contain only "\n" are now ignored.
+* Various Bash 4 fixes (https://github.com/awslabs/git-secrets/issues/66).
+* Make IAM key scanning much more targeted.
+
+## 1.2.1 - 2016-06-27
+
+* Fixed an issue where secret provider commands were causing "command not
+  found" errors due to a previously set IFS variable.
+  https://github.com/awslabs/git-secrets/pull/30
+
+## 1.2.0 - 2016-05-23
+
+* Fixed an issue where spaces files with spaces in their names were not being
+  properly scanned in the pre-commit hook.
+* Now ignoring empty lines and comments (e.g., `#`) in the .gitallowed file.
+* Fixed an issue where numbers were being compared to strings causing failures
+  on some platforms.
+
+## 1.1.0 - 2016-04-06
+
+* Bug fix: the pre-commit hook previously only scanned the working directory
+  rather than staged files. This release updates the pre-commit hook to instead
+  scan staged files so that git-secrets will detect violations if the working
+  directory drifts from the staging directory.
+* Added the `--scan-history` subcommand so that you can scan your entire
+  git history for violations.
+* Added the ability to filter false positives by using a .gitallowed file.
+* Added support for `--cached`, `--no-index`, and `--untracked` to the `--scan`
+  subcommand.
+
+## 1.0.1 - 2016-01-11
+
+* Now works correctly with filenames in a repository that contain spaces when
+  executing `git secrets --scan` with no provided filename (via `git grep`).
+* Now works with git repositories with hundreds of thousands of files when
+  using `git secrets --scan` with no provided filename (via `git grep`).
+
+## 1.0.0 - 2015-12-10
+
+* Initial release of ``git-secrets``.

git-secrets/CODE_OF_CONDUCT.md

@@ -0,0 +1,4 @@
+## Code of Conduct
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
+[email protected] with any additional questions or comments.

git-secrets/CONTRIBUTING.md

@@ -0,0 +1,61 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional 
+documentation, we greatly value feedback and contributions from our community.
+
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary 
+information to effectively respond to your bug report or contribution.
+
+
+## Reporting Bugs/Feature Requests
+
+We welcome you to use the GitHub issue tracker to report bugs or suggest features.
+
+When filing an issue, please check [existing open](https://github.com/awslabs/git-secrets/issues), or [recently closed](https://github.com/awslabs/git-secrets/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already 
+reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+
+* A reproducible test case or series of steps
+* The version of our code being used
+* Any modifications you've made relevant to the bug
+* Anything unusual about your environment or deployment
+
+
+## Contributing via Pull Requests
+Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
+
+1. You are working against the latest source on the *master* branch.
+2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
+3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
+
+To send us a pull request, please:
+
+1. Fork the repository.
+2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
+3. Ensure local tests pass.
+4. Commit to your fork using clear commit messages.
+5. Send us a pull request, answering any default questions in the pull request interface.
+6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and 
+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
+
+
+## Finding contributions to work on
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/awslabs/git-secrets/labels/help%20wanted) issues is a great place to start. 
+
+
+## Code of Conduct
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
+[email protected] with any additional questions or comments.
+
+
+## Security issue notifications
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
+
+
+## Licensing
+
+See the [LICENSE](https://github.com/awslabs/git-secrets/blob/master/LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+
+We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.