Configure Github repos from a central Terraform component using the Terraform Github provider

[sebastian-sommerfeld-io]

• UseTerraform Github Provider (https://registry.terraform.io/providers/integrations/github/latest/docs)
  • Declare each repo separately ... Since most repos do not share DockerHub secrets etc. They cannot be handled equally anyway. By handling them separately I can define every repo in its entirety.
    • Include files for common settings where ever possible (labels)
      • Take a look at: https://blog.gruntwork.io/how-to-create-reusable-infrastructure-with-terraform-modules-25526d65f73d
      • Take a look at: https://developer.hashicorp.com/terraform/tutorials/modules
  • [x] Don't implement / duplicate in pipeline! Delegate to the bash scripts!
  • [x] refactor terraform main.tf -> one file per module instead of a long main.tf
  • [x] #29
  • [x] Set issue labels
    • [x] Remove pipelines from projects and labels template from jarvis
  • Run from Github Actions -> "Apply global Github Config" (filename = configure-github.yml)
    • [x] Run scheduled (weekly)
    • [x] Run when terraform files or the workflow file change
    • [x] Add manual trigger to allow setup of new repos when needed (without waiting a week for the trigger to kick in)
    • [x] Validate terraform code
    • [x] Auto-format and commit terraform code
    • [x] #28
      • [x] #27
    • [x] terraform plan before terraform apply
    • [x] #35
    • Does docker run work with --user setting in Github Action?
  • [x] Use Action Secret "TERRAFORM in config repo and use in Guthub Actions Workflow ... make sure scripts from localhost work (get the token from somewhere else)
• [x] Add a local simulate-pipeline.sh script (or similar) -> run all steps in sequenz similar like the pipeline does
  • [x] Introduce token as second param for apply-config.sh ... Pass ${{ secret.XXX }} in pipeline and the local token as an argument
  • [x] Use $LOG_ERROR and $LOG_INFOfrom localhost and from pipeline
• [x] #23
• [x] Add a terraform linter https://github.com/terraform-linters/tflint
• [x] Check if refactoring pipelines is possible (based on this issue). Is something obsolete now (other than the jarvis module)?
• [x] Create Tag & Release: v0.1.0
• Write docs
  • [x] Remove Github contents from onboardings.adoc
  • [x] Move to github/config.adoc
  • [x] Plantuml
  • [x] Write down which secrets must be added manually (for config repo ... all other repos are configured by terraform)
  • [x] Maybe: Auto-convert help.adoc into partial
    • [x] Include the partial in the generated apply-config-sh.adoc file
• [x] #18
• [x] #31

Implementation ideas

Place files in src/main/github and and src/test/github use these tiles in pipeline. Similar to:

jobs:
  example-job:
    steps:
      - name: Run build script
        run: ./.github/scripts/build.sh
        shell: bash

See: https://docs.github.com/en/actions/learn-github-actions/essential-features-of-github-actions

Next idea

Check if I can roll out some yml-files which are the same for all repositories? Update in repo, commit and push ... The organize-*.yml github workflows should be the same for every repo.

[sebastian-sommerfeld-io]

Stack Overflow Question on creating labels based on a set of repositories: https://stackoverflow.com/questions/74812989/creating-issue-labels-with-terraform-using-the-github-provider

Seems like my issue is the same as this open Issue in the official project: https://github.com/integrations/terraform-provider-github/issues/1238