Initial commit

.envrc

@@ -0,0 +1,7 @@
+#
+# https://direnv.net/
+#
+
+pre-commit install
+
+source_env_if_exists .envrc.private

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @opsd-io/terraformers

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,58 @@
+name: Bug report
+description: File a bug/issue
+title: "[BUG]: "
+labels: ["bug"]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Are there other open or closed issues or Pull Requests that match your issue?
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Current Behavior
+    description: In a few words, describe the problem you are struggling with.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: A concise description of what you expected to happen.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Steps To Reproduce
+    description: Steps to reproduce the behavior.
+    placeholder: |
+      1. In this environment...
+      2. With this config...
+      3. Run '...'
+      4. See error...
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Environment
+    description: |
+      examples:
+        - **Terraform version**: 1.3.0
+        - **Terraform provider version**: 4.0
+    value: |
+        - Terraform version: 0.0.0
+        - Terraform provider version: 0.0
+    render: markdown
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Anything else?
+    description: |
+      Links? References? Anything that will give us more context about the issue you are encountering!
+
+      **Tip**: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+      **Tip**: You can use GitHub Gist to share debug output.
+  validations:
+    required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Join to the OPSd community on Slack
+    url: https://join.slack.com/t/opsd-community/signup
+    about: If you want to contact us personally join our Slack.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,40 @@
+name: Feature request
+description: Suggest new functionality
+title: "[FEATURE]: "
+labels: ["enhancement"]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Are there other open or closed issues or Pull Requests that match your suggestion?
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Is your feature request related to a problem? Please describe
+    description: A clear and concise description of what the problem is.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Describe the solution you'd like
+    description: A clear and concise description of what you want to happen.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Describe alternatives you've considered
+    description: A clear and concise description of any alternative solutions or features you've considered.
+  validations:
+    required: true
+- type: textarea
+  attributes:
+    label: Anything else?
+    description: |
+      Links? References? Mockups? Anything that will give us more context about the feature you are encountering!
+
+      **Tip**: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+      **Tip**: You can use GitHub Gist to share your concepts/ideas.
+  validations:
+    required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+## What changes does your PR bring?
+
+In a few words, describe what changes your commits make to the code.
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] Chore (non-breaking change to the build process or auxiliary tools)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Documentation (Improvements or additions to documentation)
+- [ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)
+
+## References
+
+Fixes:
+
+# Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented on my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules