Merge pull request #1 from ultimateai/PLT-356

major: PLT-356 Rolling out workload identity k8s

Author: avinashsi

.github/workflows/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,29 @@
+# Copyright 2022 Google LLC
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# 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.
+
+name: "Close stale issues"
+on:
+  schedule:
+  - cron: "0 23 * * *"
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/stale@v7
+      with:
+        repo-token: ${{ secrets.ULTIMATE_GITHUB_PAT }}
+        stale-issue-message: 'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days'
+        stale-pr-message: 'This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days'
+        exempt-issue-labels: triaged

.github/workflows/stale.yml

@@ -7,70 +7,17 @@ on:
   pull_request:
 
 jobs:
-  terraform:
-    name: "Terraform"
+  check_format:
     runs-on: ubuntu-latest
+    name: Check terraform file are formatted correctly
     steps:
       - name: Checkout
         uses: actions/checkout@v2
 
-      - name: Setup Terraform
-        uses: hashicorp/setup-terraform@v1
-        with:
-          terraform_version: 0.15.5
-          cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}
+      - name: terraform fmt
+        uses: dflook/terraform-fmt-check@v1
+        id: fmt-check
 
-      - name: Terraform Format
-        id: fmt
-        run: terraform fmt -check
-
-      - name: Terraform Init
-        id: init
-        run: terraform init
-      
-      - name: Terraform Validate
-        id: validate
-        run: terraform validate -no-color
-
-      - name: Terraform Plan
-        id: plan
-        if: github.event_name == 'pull_request'
-        run: terraform plan -no-color
-        continue-on-error: true
-
-      - uses: actions/github-script@v4
-        if: github.event_name == 'pull_request'
-        env:
-          PLAN: "terraform\n${{ steps.plan.outputs.stdout }}"
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          script: |
-            const output = `#### Terraform Format and Style 🖌\`${{ steps.fmt.outcome }}\`
-            #### Terraform Initialization ⚙️\`${{ steps.init.outcome }}\`
-            #### Terraform Validation 🤖\`${{ steps.validate.outputs.stdout }}\`
-            #### Terraform Plan 📖\`${{ steps.plan.outcome }}\`
-
-            <details><summary>Show Plan</summary>
-
-            \`\`\`\n
-            ${process.env.PLAN}
-            \`\`\`
-
-            </details>
-
-            *Pusher: @${{ github.actor }}, Action: \`${{ github.event_name }}\`*`;
-
-            github.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: output
-            })
-
-      - name: Terraform Plan Status
-        if: steps.plan.outcome == 'failure'
-        run: exit 1
-
-      - name: Terraform Apply
-        if: github.ref == 'refs/heads/main' && github.event_name == 'push'
-        run: terraform apply -auto-approve
+      - name: Wrong formatting found
+        if: ${{ failure() && steps.fmt-check.outputs.failure-reason == 'check-failed' }}
+        run: echo "terraform formatting check failed"

.github/workflows/terraform.yml

@@ -1,38 +1,17 @@
-fail_fast: false
 repos:
-  - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v2.3.0
+  - repo: https://github.com/mineiros-io/pre-commit-hooks
+    rev: v0.4.1
     hooks:
-      - id: check-yaml
-      - id: end-of-file-fixer
-        exclude: README.md
-      - id: trailing-whitespace
-        exclude: README.md
-      - id: detect-aws-credentials
-      - id: detect-private-key
-  - repo: local
-    hooks:
-      - id: terraform_lint
-        name: Terraform lint
-        entry: make lint
-        language: system
-      - id: terraform_fmt
-        name: Terraform format
-        entry: make fmt
-        language: system
-      - id: terraform_validate
-        name: Terraform validate
-        entry: make validate
-        language: system
-      - id: terraform_sec
-        name: Terraform security
-        entry: make security
-        language: system
-      - id: terraform_checkov
-        name: Terraform static code analysis tool
-        entry: make checkov
-        language: system
-      - id: terraform_docs
-        name: Terraform documentation
-        entry: make docs
-        language: system
+      - id: terraform-fmt
+      - id: terraform-validate
+        exclude: ^examples|.terraform/
+      - id: tflint
+      - id: phony-targets
+      - id: terradoc-validate
+      - id: golangci-lint
+      - id: terradoc-fmt
+      - id: terradoc-generate
+      # - id: terramate-generate
+      - id: markdown-link-check
+        args: ['-p']   # When adding the -p flag, markdown-link-check will always with an exit code 0, even if dead links are found
+        verbose: true  # Forces the output of the hook to be printed even when the hook passes.

.pre-commit-config.yaml

@@ -1,6 +1,6 @@
 # Terraform docs configuration file
 formatter: markdown table
-header-from: doc.md
+header-from: Terraform-docs.md
 sort:
   enabled: true
 sections:

.terraform-docs.yml

@@ -0,0 +1 @@
+* @ultimateai/platform-engineering

.terraform.lock.hcl

@@ -0,0 +1,90 @@
+# Contribution Guidelines
+
+First and foremost, we’d like to express our gratitude to you for taking the time to contribute.
+We welcome and appreciate any and all contributions via
+[Pull Requests] along the [GitHub Flow].
+
+- [Contribution Guidelines](#contribution-guidelines)
+  - [Open a GitHub issue](#open-a-github-issue)
+  - [Fork the repository on GitHub](#fork-the-repository-on-github)
+  - [Install the pre-commit hooks](#install-the-pre-commit-hooks)
+  - [Update the documentation](#update-the-documentation)
+  - [Update the tests](#update-the-tests)
+  - [Update the code](#update-the-code)
+  - [Create a pull request](#create-a-pull-request)
+  - [Merge and release](#merge-and-release)
+
+## Open a GitHub issue
+
+For bug reports or requests, please submit your issue in the appropriate repository.
+
+We advise that you open an issue and ask the
+[CODEOWNERS] and community prior to starting a contribution.
+This is your chance to ask questions and receive feedback before
+writing (potentially wrong) code. We value the direct contact with our community
+a lot, so don't hesitate to ask any questions.
+
+## Fork the repository on GitHub
+
+[Fork] the repository into your own GitHub account and [create a new branch] as
+described in the [GitHub Flow].
+
+## Install the pre-commit hooks
+
+If the repository you're working on ships with a
+[`.pre-commit-config.yaml`][pre-commit-file],
+make sure the necessary hooks have been installed before you begin working
+(e.g. a `pre-commit install`).
+
+## Update the documentation
+
+We encourage you to update the documentation before writing any code (please see
+[Readme Driven Development]. This ensures the
+documentation stays up to date and allows you to think through the problem fully before you begin implementing any
+changes.
+
+## Update the tests
+
+We also recommend updating the automated tests before updating any code
+(see [Test Driven Development](https://en.wikipedia.org/wiki/Test-driven_development)).
+
+That means that you should add or update a test case, run all tests and verify
+that the new test fails with a clear error message and then start implementing
+the code changes to get that test to pass.
+
+The test folder in every repository will have documentation on how to run the
+tests locally.
+
+## Update the code
+
+At this point, make your code changes and constantly test again your new test case to make sure that everything working
+properly. Do [commit] early and often and make useful commit messages.
+
+If a backwards incompatible change cannot be avoided, please make sure to call that out when you submit a pull request,
+explaining why the change is absolutely necessary.
+
+## Create a pull request
+
+[Create a pull request] with your changes.
+Please make sure to include the following:
+
+1. A description of the change, including a link to your GitHub issue.
+1. Any notes on backwards incompatibility or downtime.
+
+## Merge and release
+
+The [CODEOWNERS] of the repository will review your code and provide feedback.
+If everything looks good, they will merge the code and release a new version while following the principles of [Semantic Versioning (SemVer)].
+
+<!-- References -->
+
+[github flow]: https://guides.github.com/introduction/flow/
+[codeowners]: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
+[fork]: https://help.github.com/en/github/getting-started-with-github/fork-a-repo
+[create a new branch]: https://guides.github.com/introduction/flow/
+[readme driven development]: https://tom.preston-werner.com/2010/08/23/readme-driven-development.html
+[commit]: https://help.github.com/en/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project
+[create a pull request]: https://help.github.com/articles/creating-a-pull-request/
+[semantic versioning (semver)]: https://semver.org/
+[pull requests]: https://github.com/mineiros-io/terraform-github-repository/pulls
+[pre-commit-file]: https://github.com/mineiros-io/terraform-github-repository/blob/main/.pre-commit-config.yaml