Initial commit

.gitignore

@@ -0,0 +1,11 @@
+*.swp
+__pycache__
+.pytest_cache
+.venv
+*.egg-info
+.coverage
+.markdownlint*
+# CDK asset staging directory
+.cdk.staging
+cdk.out
+cdk.context.json

.pre-commit-config.yaml

@@ -0,0 +1,74 @@
+repos:
+  - repo: https://github.com/pycqa/isort
+    rev: 5.10.1
+    hooks:
+      - id: isort
+        args: ["--profile", "black"]
+        verbose: true
+  - repo: https://github.com/psf/black
+    rev: 21.12b0 # Replace with any tag/version: https://github.com/psf/black/tags
+    hooks:
+      - id: black
+        language_version: python3 # Should be a command that runs python3.7+
+        verbose: true
+  - repo: https://gitlab.com/pycqa/flake8
+    rev: 4.0.1
+    hooks:
+      - id: flake8
+        args: ['--max-line-length=150', '--ignore=E203, A002', '--max-cognitive-complexity=14', '--max-expression-complexity=7' ]
+        additional_dependencies: [
+          flake8-bugbear, # Detect potential bugs
+          flake8-builtins, # Check for built-ins being used as variables
+          flake8-cognitive-complexity, # Check max function complexity
+          flake8-comprehensions, # Suggestions for better list/set/dict comprehensions 
+          flake8-eradicate, # Find dead/commented out code
+          flake8-expression-complexity, # Check max expression complexity
+          flake8-fixme, # Check for FIXME, TODO, and XXX left in comments
+          flake8-logging-format, # Validate (lack of) logging format strings
+          flake8-mutable, # Check for mutable default arguments
+          flake8-pie, # Misc. linting rules
+          flake8-pytest-style, # Check against pytest style guide
+          flake8-return, # Check return statements
+          flake8-simplify, # Suggestions to simplify code
+          flake8-use-fstring, # Encourages use of f-strings vs old style
+          pep8-naming, # Check PEP8 class naming
+        ]
+        verbose: true
+  - repo: https://github.com/Lucas-C/pre-commit-hooks-safety
+    rev: v1.2.2
+    hooks:
+    - id: python-safety-dependencies-check
+      verbose: true
+  - repo: https://github.com/awslabs/git-secrets
+    rev: 80230afa8c8bdeac766a0fece36f95ffaa0be778
+    hooks:
+      - id: git-secrets
+        verbose: true
+        entry: 'git-secrets --register-aws'
+        language: script
+        name: git-secrets-register-aws-provider
+      - id: git-secrets
+        verbose: true
+        entry: 'git-secrets --scan'
+        language: script
+        name: git-secrets-scan
+  - repo: https://github.com/markdownlint/markdownlint
+    rev: v0.11.0
+    hooks:
+      - id: markdownlint
+        name: Markdownlint
+        description: Run markdownlint on your Markdown files
+        entry: mdl .
+        language: ruby
+        files: \.(md|mdown|markdown)$
+        verbose: true
+        args:
+          - "-s"
+          - "mdl_style.rb"
+  - repo: https://github.com/PyCQA/bandit
+    rev: '1.7.1'
+    hooks:
+      - id: bandit
+        entry: bandit
+        exclude: ^tests/
+        verbose: true

CODE_OF_CONDUCT.md

@@ -0,0 +1,6 @@
+# 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
+opensource-codeofconduct@amazon.com with any additional questions or comments.

CONTRIBUTING.md

@@ -0,0 +1,78 @@
+# 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, or recently closed,
+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.
+This repository use [pre-commit](https://pre-commit.com/) hooks for linting.
+Before sending us a pull request, please ensure that:
+
+1. You are working against the latest source on the *main* branch.
+1. You check existing open, and recently merged,
+    pull requests to make sure someone else hasn't addressed the problem already.
+1. 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.
+1. 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.
+1. Ensure local tests pass.
+1. Commit to your fork using clear commit messages.
+1. Send us a pull request, answering any default questions in the pull request interface.
+1. Pay attention to any automated CI failures reported in the pull request,
+    and stay involved in the conversation.
+
+> Note: you may need to update the commit if `pre-commit` changes/suggests changes to files
+
+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' 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
+opensource-codeofconduct@amazon.com 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](LICENSE) file for our project's licensing.
+We will ask you to confirm the licensing of your contribution.

LICENSE

@@ -0,0 +1,15 @@
+Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+
+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.
+
+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.
+