-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outputting plan file to specific path fails #55
Comments
Hi @Mornor, the issue is the forward slash, right? |
Yes, it should work with a forward slash (so a full path) like so
But it doesn't ( However, this works (without forward slash)
IMO, we should be able to give a full path for the plan file as output. |
The corresponding command (
However, it seems the terragrunt command itself doesn't work as expected. Locally, this does not produce any plan.
But this does
However, not with Github Action ( This might be related to a core Terragrunt issue. |
Hi,
when during execution, working directory is mounted in |
Hi @denis256, Big up to you, as I managed to make it work with a combination of your solution and some - name: Plan
uses: gruntwork-io/terragrunt-action@v2
with:
tf_version: ${{ inputs.tf_version }}
tg_version: ${{ inputs.tg_version }}
tg_dir: ${{ inputs.customer_dir }}/${{ inputs.customer }}/${{ inputs.dir_to_deploy }}
tg_command: plan -out /github/workspace/terragrunt.tfplan
- name: Move plan file
working-directory: ${{ github.workspace }}
run: mv terragrunt.tfplan ${{ inputs.customer_dir }}/${{ inputs.customer }}/${{ inputs.dir_to_deploy }}/terragrunt.tfplan I don't really like or understand the combination of |
Closing this issue as it is related to how the GitHub action sets up the workspace directory. |
Describe the bug
The following commands fails to redirect the plan file
To Reproduce
Expected behavior
Actual behaviour
Other notes
The following command works
But I would expect one of these commands to work instead
Nice to have
Versions
terragrunt-action@v2
Related
Might be related to #40
The text was updated successfully, but these errors were encountered: