chore: clean github templates [skip ci]

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -0,0 +1,88 @@
+name: Bug report
+description: Create a bug report
+title: "[terraform] Bug title"
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: Please be cautious with the sensitive information/logs while filing the issue.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the bug a clear and concise description of what the bug is.
+    validations:
+      required: true
+
+  - type: input
+    id: ansible-version
+    attributes:
+      label: What's your ansible version?
+      description: Output of `#~ ansible version`
+    validations:
+      required: true
+
+  - type: input
+    id: terraform-name
+    attributes:
+      label: terraform name
+      description: Enter the name of the terraform where you encountered this bug.
+    validations:
+      required: true
+
+  - type: input
+    id: terraform-version
+    attributes:
+      label: terraform version
+      description: Enter the version of the terraform that you encountered this bug.
+    validations:
+      required: true
+
+  - type: textarea
+    id: explain-bug
+    attributes:
+      label: Explain bug
+      description: Explain what happened.
+    validations:
+      required: false
+
+  - type: textarea
+    id: expected-result
+    attributes:
+      label: What you expected to happen?
+      description: Enter what you expected to happen.
+    validations:
+      required: false
+
+  - type: textarea
+    id: reproduce-bug
+    attributes:
+      label: How to reproduce it?
+      description: Explain step-by-step if is possible.
+    validations:
+      required: false
+
+  - type: textarea
+    id: terraform-values
+    attributes:
+      label: Enter the changed values
+      description: Please enter only values which differ from the defaults. Enter `NONE` if nothing's changed.
+      placeholder: 'key: value'
+    validations:
+      required: false
+
+  - type: textarea
+    id: ansible-command
+    attributes:
+      label: Enter the command that you execute when terraform failing/misfunctioning
+      description: Enter the command as-is as how you executed.
+      placeholder: terraform [...]
+    validations:
+      required: true
+
+  - type: textarea
+    id: more-info
+    attributes:
+      label: More info
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature-request.yaml

@@ -0,0 +1,40 @@
+name: Feature request
+description: Suggest an idea to improve this project
+title: "[terraform] Feature title"
+labels: [enhancement]
+body:
+  - type: markdown
+    attributes:
+      value: Thanks for taking the time to fill out this bug report!
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Is your feature request related to a problem?
+      description: Description of what the problem is.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposals
+    attributes:
+      label: Describe the solution you'd like
+      description: Description of what you want to happen.
+    validations:
+      required: true
+
+  - type: textarea
+    id: improves
+    attributes:
+      label: Describe alternatives you've considered
+      description: Description of any alternative solutions or features you've considered. If nothing, please enter `NONE`
+    validations:
+      required: true
+
+  - type: textarea
+    id: more-info
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.
+    validations:
+      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,24 @@
+<!--
+Following our best practices right from the start will accelerate the review process and help get your PR merged quicker.
+
+When updates to your PR are requested, please add new commits and do not squash the history.
+This will make it easier to identify new changes. The PR will be squashed anyways when it is merged.
+
+PR Steps:
+1) Please make sure you test your changes before you push them.
+2) Once pushed, GitHub Actions will run across your changes and do some initial checks and linting.
+3) These checks run very quickly.
+4) Please check the results.
+5) We would like these checks to pass before we even continue reviewing your changes.
+-->
+#### What this PR does / why we need it:
+
+#### Which issue this PR fixes
+*(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*
+  - fixes #
+
+#### Special notes for your reviewer:
+
+#### Checklist
+<!-- [Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->
+- [ ] Title of the PR starts with Terraform role name

.github/dependabot.yml

@@ -0,0 +1,27 @@
+version: 2
+updates:
+- package-ecosystem: github-actions
+  directory: "/"
+  schedule:
+    interval: monthly
+  open-pull-requests-limit: 10
+  labels:
+  - enhancement
+  - dependency-management
+- package-ecosystem: terraform
+  directories:
+  - "/terraform/**/*"
+  schedule:
+    interval: monthly
+  open-pull-requests-limit: 10
+  labels:
+  - enhancement
+  - dependency-management
+- package-ecosystem: pip
+  directory: "/virtualenvs"
+  schedule:
+    interval: monthly
+  open-pull-requests-limit: 10
+  labels:
+  - enhancement
+  - dependency-management

.github/workflows/auto-assign.yaml

@@ -0,0 +1,19 @@
+name: Auto assign
+on:
+  issues:
+    types: [opened]
+  pull_request:
+    types: [opened, edited, synchronize, reopened]
+jobs:
+  run:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+    - name: 'Auto-assign issue'
+      uses: pozil/auto-assign-issue@v2
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        assignees: ialejandro
+        numOfAssignee: 1