Request for support to create follow-up PRs for drift detection

[cappyzawa]

Feature Overview

Request for support to create follow-up PRs for drift detection.

Why is the feature needed?

Currently, drift detection in tfaction creates GitHub Issues to track detected drifts.
While this is useful, it would be more efficient for our workflow if follow-up PRs were automatically created when a drift is detected.

Having the option to choose between managing drifts via Issues or follow-up PRs would cater to different workflow preferences and enhance flexibility.

Example Code

GitHub Actions

    steps:
    - uses: actions/[email protected]
    - uses: tibdex/[email protected]
      id: generate_token
      with:
        app_id: ${{ secrets.APP_ID }}
        private_key: ${{ secrets.APP_PRIVATE_KEY }}
    - uses: aquaproj/[email protected]
      with:
        aqua_version: v2.25.1
    - uses: suzuki-shunsuke/tfaction/[email protected]
      with:
        secrets: ${{ toJSON(secrets) }}
    - uses: suzuki-shunsuke/tfaction/[email protected]
      id: setup
      with:
        github_token: ${{ steps.generate_token.outputs.token }}
    - uses: suzuki-shunsuke/tfaction/[email protected]
      with:
        github_token: ${{ steps.generate_token.outputs.token }}
    - uses: suzuki-shunsuke/tfaction/[email protected]
      with:
        github_token: ${{ steps.generate_token.outputs.token }}
      env:
        TF_VAR_github_app_token: ${{ steps.generate_token.outputs.token }}
    - uses: suzuki-shunsuke/tfaction/[email protected]
      if: failure()
      with:
        github_token: ${{ steps.generate_token.outputs.token }}

Note

No response