@denis256 let me know if this is ok, or if I need to add something else, or if this is a no go. I tested with some internal repos and worked like a charm.

It requires approval from someone who have write access to the project. Not my case unfortunately. But the implementation looks great to me.

It requires approval from someone who have write access to the project. Not my case unfortunately. But the implementation looks great to me.

Got it, thanks for clarifying!

This is a good solution to get Python rolling, but another solution to this problem is simply to useINPUT_PRE_EXEC_number. Example:

      - name: Run ${{ inputs.terragrunt-command }} in the Terragrunt project
        uses: gruntwork-io/terragrunt-action@v2
        with:
          tf_version: ${{ inputs.terraform-version }}
          tg_version: ${{ inputs.terragrunt-version }}
          tg_dir: ${{ inputs.terragrunt-directory }}
          tg_command: "${{ inputs.terragrunt-command }} --terragrunt-working-dir ${{ inputs.terragrunt-working-dir }}"
        env:
          INPUT_PRE_EXEC_1: "sudo apt update -y && sudo apt install -y python3"