Update terragrunt.hcl

[motatoes]

No description provided.

[digger-app-1932760430]

Project	Layer
🕚 core/network	0
🕚 layer1/compute	1
🕚 layer1/monitoring	1
🕚 layer1/storage	1

---

Instructions

Since you enabled layers in your configuration, you can proceed to perform a layer-by-layer deployment.
To start planning the first layer you can run "digger plan --layer 0". To apply the first layer, run "digger apply --layer 0".

To deploy the next layer, run "digger plan --layer 1". To apply the next layer, run "digger apply --layer 1".

And so on. A new commit on the branch will restart this deployment process.

[motatoes]

terragrunt plan

[motatoes]

digger plan

[digger-app-1932760430]

Project	Status	Plan	+	~	-
✅ layer1_monitoring	succeeded	Plan	0	0	0
✅ core_network	succeeded	Plan	0	0	0
✅ layer1_compute	succeeded	Plan	0	0	0
✅ layer1_storage	succeeded	Plan	0	0	0

Instructions

⏩ To apply these changes, run the following command:

digger apply

🚮 To unlock the projects in this PR run the following command:

digger unlock

[digger-app-1932760430]

Project	Layer
🕚 core/network	0
🕚 layer1/compute	1
🕚 layer1/monitoring	1
🕚 layer1/storage	1
🕚 layer2/analytics	2

---

Instructions

Since you enabled layers in your configuration, you can proceed to perform a layer-by-layer deployment.
To start planning the first layer you can run "digger plan --layer 0". To apply the first layer, run "digger apply --layer 0".

To deploy the next layer, run "digger plan --layer 1". To apply the next layer, run "digger apply --layer 1".

And so on. A new commit on the branch will restart this deployment process.

[motatoes]

digger plan

[digger-app-1932760430]

Project	Status	Plan	+	~	-
❌ layer2_analytics	failed	Plan	0	0	0
✅ core_network	succeeded	Plan	0	0	0
✅ layer1_storage	succeeded	Plan	0	0	0
✅ layer1_monitoring	succeeded	Plan	0	0	0
✅ layer1_compute	succeeded	Plan	0	0	0

Instructions

⏩ To apply these changes, run the following command:

digger apply

🚮 To unlock the projects in this PR run the following command:

digger unlock

[digger-app-1932760430]

Project	Layer
🕚 core/network	0
🕚 layer1/compute	1
🕚 layer1/monitoring	1
🕚 layer1/storage	1
🕚 layer2/analytics	2

---

Instructions

Since you enabled layers in your configuration, you can proceed to perform a layer-by-layer deployment.
To start planning the first layer you can run "digger plan --layer 0". To apply the first layer, run "digger apply --layer 0".

To deploy the next layer, run "digger plan --layer 1". To apply the next layer, run "digger apply --layer 1".

And so on. A new commit on the branch will restart this deployment process.

[motatoes]

digger plan

[digger-app-1932760430]

Project	Status	Plan	+	~	-
✅ core_network	succeeded	Plan	0	0	0
✅ layer1_storage	succeeded	Plan	0	0	0
✅ layer1_monitoring	succeeded	Plan	0	0	0
✅ layer1_compute	succeeded	Plan	0	0	0
❌ layer2_analytics	failed	Plan	0	0	0

Instructions

⏩ To apply these changes, run the following command:

digger apply

🚮 To unlock the projects in this PR run the following command:

digger unlock

[github-actions]

plan for layer2_analytics 2025-08-20 01:11:44 (UTC)

Error during init.

01:11:46.839 WARN Using `terragrunt.hcl` as the root of Terragrunt configurations is an anti-pattern, and no longer recommended. In a future version of Terragrunt, this will result in an error. You are advised to use a differently named file like `root.hcl` instead. For more information, see https://terragrunt.gruntwork.io/docs/migrate/migrating-from-root-terragrunt-hcl 01:11:47.908 WARN [../../layer1/compute] Config ../../core/security/terragrunt.hcl is a dependency of ../../layer1/compute/terragrunt.hcl that has no outputs, but mock outputs provided and returning those in dependency output. 01:11:48.224 WARN [../../layer1/storage] Config ../../core/security/terragrunt.hcl is a dependency of ../../layer1/storage/terragrunt.hcl that has no outputs, but mock outputs provided and returning those in dependency output. 01:11:48.243 WARN [../../layer1/monitoring] Config ../../core/security/terragrunt.hcl is a dependency of ../../layer1/monitoring/terragrunt.hcl that has no outputs, but mock outputs provided and returning those in dependency output.

Error: Required plugins are not installed

The installed provider plugins are not consistent with the packages selected
in the dependency lock file:

• registry.terraform.io/hashicorp/null: the cached package for registry.terraform.io/hashicorp/null 3.2.4 (in .terraform/providers) does not match any of the checksums recorded in the dependency lock file

Terraform uses external plugins to integrate with a variety of different
infrastructure services. You must install the required plugins before running
Terraform operations.
01:11:49.690 ERROR Failed to execute "terraform output -json" in ../../layer1/storage/.terragrunt-cache/2212392471

Error: Required plugins are not installed

The installed provider plugins are not consistent with the packages selected
in the dependency lock file:

• registry.terraform.io/hashicorp/null: the cached package for registry.terraform.io/hashicorp/null 3.2.4 (in .terraform/providers) does not match any of the checksums recorded in the dependency lock file

Terraform uses external plugins to integrate with a variety of different
infrastructure services. You must install the required plugins before running
Terraform operations.

exit status 1

[digger-app-1932760430]

Project	Layer
🕚 core/network	0
🕚 core/security	0
🕚 layer1/compute	1
🕚 layer1/monitoring	1
🕚 layer1/storage	1
🕚 layer2/analytics	2
🕚 layer2/api	2
🕚 layer2/frontend	2

---

Instructions

Since you enabled layers in your configuration, you can proceed to perform a layer-by-layer deployment.
To start planning the first layer you can run "digger plan --layer 0". To apply the first layer, run "digger apply --layer 0".

To deploy the next layer, run "digger plan --layer 1". To apply the next layer, run "digger apply --layer 1".

And so on. A new commit on the branch will restart this deployment process.

[motatoes]

digger plan --layer 2

[digger-app-1932760430]

Project	Status	Plan	+	~	-
❌ layer2_frontend	failed	Plan	0	0	0
✅ layer2_api	succeeded	Plan	0	0	1
❌ layer2_analytics	failed	Plan	0	0	0

Instructions

⏩ To apply these changes, run the following command:

digger apply

🚮 To unlock the projects in this PR run the following command:

digger unlock

[github-actions]

plan for layer2_analytics 2025-08-20 01:18:06 (UTC)

Error during init.

01:18:09.322 WARN Using `terragrunt.hcl` as the root of Terragrunt configurations is an anti-pattern, and no longer recommended. In a future version of Terragrunt, this will result in an error. You are advised to use a differently named file like `root.hcl` instead. For more information, see https://terragrunt.gruntwork.io/docs/migrate/migrating-from-root-terragrunt-hcl 01:18:10.174 WARN [../../layer1/compute] Config ../../core/security/terragrunt.hcl is a dependency of ../../layer1/compute/terragrunt.hcl that has no outputs, but mock outputs provided and returning those in dependency output. 01:18:10.467 WARN [../../layer1/storage] Config ../../core/security/terragrunt.hcl is a dependency of ../../layer1/storage/terragrunt.hcl that has no outputs, but mock outputs provided and returning those in dependency output. 01:18:10.485 WARN [../../layer1/monitoring] Config ../../core/security/terragrunt.hcl is a dependency of ../../layer1/monitoring/terragrunt.hcl that has no outputs, but mock outputs provided and returning those in dependency output.

Error: Required plugins are not installed

The installed provider plugins are not consistent with the packages selected
in the dependency lock file:

• registry.terraform.io/hashicorp/null: the cached package for registry.terraform.io/hashicorp/null 3.2.4 (in .terraform/providers) does not match any of the checksums recorded in the dependency lock file

Terraform uses external plugins to integrate with a variety of different
infrastructure services. You must install the required plugins before running
Terraform operations.

Error: Required plugins are not installed

The installed provider plugins are not consistent with the packages selected
in the dependency lock file:

• registry.terraform.io/hashicorp/null: the cached package for registry.terraform.io/hashicorp/null 3.2.4 (in .terraform/providers) does not match any of the checksums recorded in the dependency lock file

Terraform uses external plugins to integrate with a variety of different
infrastructure services. You must install the required plugins before running
Terraform operations.
01:18:11.806 ERROR Failed to execute "terraform output -json" in ../../layer1/storage/.terragrunt-cache/1957781742

Error: Required plugins are not installed

The installed provider plugins are not consistent with the packages selected
in the dependency lock file:

• registry.terraform.io/hashicorp/null: the cached package for registry.terraform.io/hashicorp/null 3.2.4 (in .terraform/providers) does not match any of the checksums recorded in the dependency lock file

Terraform uses external plugins to integrate with a variety of different
infrastructure services. You must install the required plugins before running
Terraform operations.

exit status 1

[github-actions]

plan for layer2_api 2025-08-20 01:18:08 (UTC)

Plan output

Terraform will perform the following actions:

  # null_resource.test will be destroyed
  # (because null_resource.test is not in configuration)
  - resource "null_resource" "test" {
      - id = "2576809280527304590" -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Terraform plan validation check (layer2_api)

Terraform plan validation checks succeeded ✅

Plan summary

CHANGE	RESOURCE
delete	null_resource.test

Instructions

▶️ To apply these changes, run the following command:

digger apply -p layer2_api

⏩ To apply all changes in this PR:

digger apply

🚮 To unlock all projects in this PR:

digger unlock

[github-actions]

plan for layer2_frontend 2025-08-20 01:18:14 (UTC)

Error during init.

01:18:17.395 WARN Using `terragrunt.hcl` as the root of Terragrunt configurations is an anti-pattern, and no longer recommended. In a future version of Terragrunt, this will result in an error. You are advised to use a differently named file like `root.hcl` instead. For more information, see https://terragrunt.gruntwork.io/docs/migrate/migrating-from-root-terragrunt-hcl 01:18:19.891 WARN [../../layer1/storage] Config ../../core/security/terragrunt.hcl is a dependency of ../../layer1/storage/terragrunt.hcl that has no outputs, but mock outputs provided and returning those in dependency output. 01:18:20.239 WARN [../../layer1/monitoring] Config ../../core/security/terragrunt.hcl is a dependency of ../../layer1/monitoring/terragrunt.hcl that has no outputs, but mock outputs provided and returning those in dependency output.

Error: Required plugins are not installed

The installed provider plugins are not consistent with the packages selected
in the dependency lock file:

• registry.terraform.io/hashicorp/null: the cached package for registry.terraform.io/hashicorp/null 3.2.4 (in .terraform/providers) does not match any of the checksums recorded in the dependency lock file

Terraform uses external plugins to integrate with a variety of different
infrastructure services. You must install the required plugins before running
Terraform operations.
01:18:23.160 ERROR Failed to execute "terraform output -json" in ../../layer1/storage/.terragrunt-cache/3859381635

Error: Required plugins are not installed

The installed provider plugins are not consistent with the packages selected
in the dependency lock file:

• registry.terraform.io/hashicorp/null: the cached package for registry.terraform.io/hashicorp/null 3.2.4 (in .terraform/providers) does not match any of the checksums recorded in the dependency lock file

Terraform uses external plugins to integrate with a variety of different
infrastructure services. You must install the required plugins before running
Terraform operations.

exit status 1

[digger-app-1932760430]

Project	Layer
🕚 core/network	0
🕚 core/security	0
🕚 layer1/compute	1
🕚 layer1/monitoring	1
🕚 layer1/storage	1
🕚 layer2/analytics	2
🕚 layer2/api	2
🕚 layer2/frontend	2

---

Instructions

Since you enabled layers in your configuration, you can proceed to perform a layer-by-layer deployment.
To start planning the first layer you can run "digger plan --layer 0". To apply the first layer, run "digger apply --layer 0".

To deploy the next layer, run "digger plan --layer 1". To apply the next layer, run "digger apply --layer 1".

And so on. A new commit on the branch will restart this deployment process.

[digger-app-1932760430]

Project	Layer
🕚 core/network	0
🕚 core/security	0
🕚 layer1/compute	1
🕚 layer1/monitoring	1
🕚 layer1/storage	1
🕚 layer2/analytics	2
🕚 layer2/api	2
🕚 layer2/frontend	2

---

Instructions

Since you enabled layers in your configuration, you can proceed to perform a layer-by-layer deployment.
To start planning the first layer you can run "digger plan --layer 0". To apply the first layer, run "digger apply --layer 0".

To deploy the next layer, run "digger plan --layer 1". To apply the next layer, run "digger apply --layer 1".

And so on. A new commit on the branch will restart this deployment process.

[motatoes]

digger plan --layer 2

[digger-app-1932760430]

Project	Status	Plan	+	~	-
❌ layer2_analytics	failed	Plan	0	0	0
✅ layer2_api	succeeded	Plan	0	0	1
✅ layer2_frontend	succeeded	Plan	0	0	1

Instructions

⏩ To apply these changes, run the following command:

digger apply

🚮 To unlock the projects in this PR run the following command:

digger unlock

[github-actions]

plan for layer2_api 2025-08-20 01:20:57 (UTC)

Plan output

Terraform will perform the following actions:

  # null_resource.test will be destroyed
  # (because null_resource.test is not in configuration)
  - resource "null_resource" "test" {
      - id = "2576809280527304590" -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Terraform plan validation check (layer2_api)

Terraform plan validation checks succeeded ✅

Plan summary

CHANGE	RESOURCE
delete	null_resource.test

Instructions

▶️ To apply these changes, run the following command:

digger apply -p layer2_api

⏩ To apply all changes in this PR:

digger apply

🚮 To unlock all projects in this PR:

digger unlock

[github-actions]

plan for layer2_frontend 2025-08-20 01:21:15 (UTC)

Plan output

Terraform will perform the following actions:

  # null_resource.testtest will be destroyed
  # (because null_resource.testtest is not in configuration)
  - resource "null_resource" "testtest" {
      - id = "137326109706552102" -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Terraform plan validation check (layer2_frontend)

Terraform plan validation checks succeeded ✅

Plan summary

CHANGE	RESOURCE
delete	null_resource.testtest

Instructions

▶️ To apply these changes, run the following command:

digger apply -p layer2_frontend

⏩ To apply all changes in this PR:

digger apply

🚮 To unlock all projects in this PR:

digger unlock

[digger-app-1932760430]

✅ Command unlock completed successfully