This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update google-github-actions/release-please-action digest to e4dc86b

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (semanticCommitTypeAll(fix))

I think that the ref: part is not useful, it automatically fetch the current ref I believe.

  - name: checkout
    uses: actions/checkout@v3
    with:
      fetch-depth: 0
      ref: ${{ github.event.pull_request.head.ref }}

There is no action to setup it ? Anyway, downloading the "latest", without fixing it may be a bit "dangerous", while useful (auto update, wow). I am quite mixed about this.

- name: tfswitch
run: |
 wget https://raw.githubusercontent.com/warrensbox/terraform-switcher/release/install.sh
 chmod 755 install.sh
 ./install.sh -b `pwd`/.bin
 rm install.sh
 CUSTOMBIN=`pwd`/.bin
 export PATH=$PATH:$CUSTOMBIN
 $CUSTOMBIN/tfswitch -b $CUSTOMBIN/terraform
 terraform -v

I personally don't like action which commits on the same place as human, I prefer only "blocking the PR". Indeed, if you want to iterate again on this PR, you'll have to git pull with the added commit from the workflow. This can be discussed

- name: terraform-docs
  uses: terraform-docs/[email protected]
  with:
    working-dir: .
    output-file: README.md
    output-method: inject
    git-commit-message: "docs: update terraform docs"
    git-push: "true"

More generally, I find this workflow OK for a module, but it would not function for a repo with layers, such as starters.

For example for a project I had a pattern such as

jobs:
  lint:
    runs-on: ubuntu-latest

    strategy:
    # needs a matrix to run it on all layers
      matrix:
        layer:
          - bootstrap
          - preprod-mybarnes
          - preprod-network
          - shared

    defaults:
      run:
        working-directory: terraform/layers/${{ matrix.layer }}

    steps:
      - uses: actions/checkout@v3

      - uses: hashicorp/setup-terraform@v2
        with:

It was not ideal since the layers list is static, but It might be a interesting use case. Does github remote workflows supports this kind of specific usage (custom workdir based on a matrix, dynamic matrix) ?

warrensbox/terraform-switcher#175

Ma CI/CD ne fonctionne plus sans aucun changement

name: Terraform quality

on: push

jobs:
  terraform-quality:
    uses: padok-team/github-workflows/.github/workflows/terraform-quality.yml@v1
    with:
      workdir: ./starters/terraform/layers