add pre-commit config and cleanup files and vars with fixed values

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,23 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Please specify the module/lab you've encountered this issue.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

github/workflows/README.md → .github/workflows.disabled/README.md

@@ -1,7 +1,7 @@
 # AWS - PSP Platform Egineering - Control Plane Automated Setup
 
 
-### For Automation use case 
+### For Automation use case
 ```mv /github ./github```
 
 ### Create OIDC Provider for Github
@@ -53,8 +53,3 @@ Use the following Trust Relationship
     ]
 }
 ```
-
-
-
-
-

github/workflows/main.yml → .github/workflows.disabled/main.yml

@@ -12,7 +12,7 @@ env:
   AWS_REGION : "us-east-1" #Change to reflect your Region
   TERRAFORM_WORKING_DIR : "terraform"
 
-# Permission can be added at job level or workflow level    
+# Permission can be added at job level or workflow level
 permissions:
       id-token: write   # This is required for requesting the JWT
       contents: read    # This is required for actions/checkout
@@ -65,19 +65,19 @@ jobs:
         id: validate
         working-directory: ${{ env.TERRAFORM_WORKING_DIR }}
         run: terraform validate -no-color
-      # - name: Terraform Destroy
-      #   working-directory: ${{ env.TERRAFORM_WORKING_DIR }}
-      #   id: destroy
-      #   run: terraform destroy -auto-approve -no-color
-      - name: Terraform Plan
-        id: plan
-        working-directory: ${{ env.TERRAFORM_WORKING_DIR }}
-        run: terraform plan -no-color
-        continue-on-error: true
-      - name: Terraform Apply
+      - name: Terraform Destroy
         working-directory: ${{ env.TERRAFORM_WORKING_DIR }}
-        id: apply
-        run: terraform apply -auto-approve -no-color
+        id: destroy
+        run: terraform destroy -auto-approve -no-color
+      # - name: Terraform Plan
+      #   id: plan
+      #   working-directory: ${{ env.TERRAFORM_WORKING_DIR }}
+      #   run: terraform plan -no-color
+      #   continue-on-error: true
+      # - name: Terraform Apply
+      #   working-directory: ${{ env.TERRAFORM_WORKING_DIR }}
+      #   id: apply
+      #   run: terraform apply -auto-approve -no-color
       # # - uses: actions/github-script@v6
       # #   if: github.event_name == 'push'
       # #   env:
@@ -89,25 +89,25 @@ jobs:
       # #       #### Terraform Initialization ⚙️\`${{ steps.init.outcome }}\`
       # #       #### Terraform Validation 🤖\`${{ steps.validate.outcome }}\`
       # #       <details><summary>Validation Output</summary>
-      
+
       # #       \`\`\`\n
       # #       ${{ steps.validate.outputs.stdout }}
       # #       \`\`\`
-      
+
       # #       </details>
-      
+
       # #       #### Terraform Plan 📖\`${{ steps.plan.outcome }}\`
-      
+
       # #       <details><summary>Show Plan</summary>
-      
+
       # #       \`\`\`\n
       # #       ${process.env.PLAN}
       # #       \`\`\`
-      
+
       # #       </details>
-      
+
       # #       *Pusher: @${{ github.actor }}, Action: \`${{ github.event_name }}\`, Working Directory: \`${{ env.TERRAFORM_WORKING_DIR }}\`, Workflow: \`${{ github.workflow }}\`*`;
-      
+
       # #       github.rest.issues.createComment({
       # #         issue_number: context.issue.number,
       # #         owner: context.repo.owner,

.gitignore

@@ -14,7 +14,7 @@
 
 # A self-extracting archive that uses the Bourne shell (sh).
 *.shar
-# A system for storing multiple files. LBR archives typically contained files processed by SQ, or the archive itself was compressed with SQ. LBR archives that were compressed with SQ ended with the extension .LQR	
+# A system for storing multiple files. LBR archives typically contained files processed by SQ, or the archive itself was compressed with SQ. LBR archives that were compressed with SQ ended with the extension .LQR
 *.LBR
 # An archive format originally used mainly for archiving and distribution of the exact, nearly-exact, or custom-modified contents of an optical storage medium such as a CD-ROM or DVD-ROM. However, it can be used to archive the contents of other storage media, selected partitions, folders, and/or files. The resulting archive is typically optimized for convenient rendering to (re-)writable CD or DVD media.
 *.iso
@@ -169,7 +169,7 @@
 # The most widely used compression format on Microsoft Windows. Commonly used on Macintosh and Unix systems as well.
 *.zip
 *.zipx
-# application/x-zoo 	zoo 	Multiple 	Multiple 	Yes 	
+# application/x-zoo 	zoo 	Multiple 	Multiple 	Yes
 *.zoo
 # Journaling (append-only) archive format with rollback capability. Supports deduplication and incremental update based on last-modified dates. Multi-threaded. Compresses in LZ77, BWT, and context mixing formats. Open source.
 *.zpaq

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

CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# 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. Before sending us a pull request, please ensure that:
+
+1. You are working against the latest source on the *main* 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' 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,16 @@
+MIT No Attribution
+
+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.