terragrunt | trigger docker build for terragrunt when new terraform | Continuous Deployment library

I would like to have checkov scan terraform plan output but I am not getting any success with that.Below is my code in terragrunt.hcl,GitHub Actions workflow and the message I got when my workflow completed.I have tried few methods to have it work but I am still unable to configure it correctly so that checkov can analyse the Json output of terraform plan.I would appreciate any help that I can get on this.Thank you for your assistance inadvance

The expectation is that when running a terragrunt run-all apply from the root directory, a provider.tf file will be created in the sub directories. I've verified my backend is able to talk to my azure storage account and it will create a terraform.tfstate file there. I expect a provider.tf file to appear under each "service#" folder. I'm extremely new to terragrunt. This is my first exercise with it. I am not actually trying to deploy any terraform resources. Just have the provider.tf file created in my sub directories. TF version is 1.1.5. Terragrunt version is 0.36.1.

my folder structure

How do I go about appending the /* to the end of an object using for_each? The goal is to have Terraform to go through the list of resource_arns and add /* to the end. However, I'm currently getting the error, "invalid template interpolation value".

If I have resources = each.value.resource_arns, then Terraform is able to create the resource, but it would just be without /*, which is not desired.

The desired outcome would be to have the resource created as:

I have a two directories: in first one I'm keeping modules (basically terraform template configurations) in the second one I'm keeping terragrunt modules implementations. In the second one there is a terragrunt hcl file with inputs inside (one for every particular project). So far I declared variables in modules directory (in variables.tf) but I don't like that as variables change depending on the implementation (project). So keeping all variables (for all projects) in the modules dir seems to be not the best idea.

My question is: how can I declare those variables on the terragrunt (aka implementations) level? Is a generate function way to go?

I'm running a Jenkins pipeline job using Jenkinsfile. The primary purpose is to run terraform , based on the choice parameter to select either plan or apply, like this:

I'm trying to iterate over a simple list of maps. Here's a segment of what my module code looks like:

Is it possible for a workflow to depend on another workflow?

I currently have 2 workflows for my test branch.The first is github_action_pull_test.yml that is triggered by a pull_request.When there is a pull_request on the test branch the workflow run to terragrunt plan.The second is github_action_push_test.yml that is triggered when there is a merge to my test branch,the workflow run terragrunt apply.

The current setup has one negative effect: my github_action_push_test.yml include all the steps in the github_action_pull_test.yml. Is there a way I can have one workflow that include all the steps but only run terragrunt apply after terragrunt plan has been reviewed and merged into the test branch so i can avoid duplications

I am hoping someone can help me with an issue I am having with Terraform/Terragrunt. The versions of each that I am currently using are:

• Terragrunt v0.35.9
• Terraform v1.0.11

I am using Terragrunt to deploy project related infrastructure to GCP. I have two seperate Terragrunt projects to split out variables between a test and a production instance of the same GCP solution.

When I run the commands terragrunt init or terragrunt plan -out tf.plan using the test .hcl file, the process completes as expected. However when I run either of these commands using the production .hcl file, I get the following error:

I am using terragrunt to call my terraform module.I have one terragrunt.hcl for my dev and another for testing environment.I would like to be able to attach AWS Managed policy(AdministratorAccess) to my Dev account and (AmazonEC2FullAccess) to my testing account using input variable so that I can remove the policy line in my aws_iam_role_policy section