Skip to content

Conversation

@motatoes
Copy link
Contributor

No description provided.

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

❌ ConvertJobsToDiggerJobs error: failed to create batch: ERROR: column "layer" of relation "digger_batches" does not exist (SQLSTATE 42703)

@motatoes motatoes closed this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

✅ Command unlock completed successfully

@motatoes motatoes reopened this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status Plan + ~ -
layer2_frontend succeeded Plan 0 0 0
layer2_analytics failed Plan 0 0 0
layer1_storage succeeded Plan 0 0 0
layer2_api succeeded Plan 0 0 0

@github-actions
Copy link

github-actions bot commented Jul 30, 2025

plan for layer2_analytics 2025-07-30 00:30:30 (UTC)
Locking successful Project diggerhq/terragrunt-layers-example#layer2_analytics has been locked by PR #4
Error during init. 00:30:32.935 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 00:30:33.745 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. 00:30:34.439 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. 00:30:34.458 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.
00:30:35.680 ERROR Failed to execute "terraform output -json" in ../../layer1/storage/.terragrunt-cache/1162456381

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

@motatoes motatoes closed this Jul 30, 2025
@motatoes motatoes reopened this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

✅ Command unlock completed successfully

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status Plan + ~ -
layer1_storage succeeded Plan 0 0 0
layer2_api succeeded Plan 0 0 0
layer2_frontend succeeded Plan 0 0 0
layer2_analytics succeeded Plan 0 0 0

@motatoes motatoes closed this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

✅ Command unlock completed successfully

@motatoes motatoes reopened this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status Plan + ~ -
layer2_analytics failed Plan 0 0 0
layer1_storage succeeded Plan 0 0 0
layer2_frontend succeeded Plan 0 0 0
layer2_api succeeded Plan 0 0 0

@github-actions
Copy link

github-actions bot commented Jul 30, 2025

plan for layer2_analytics 2025-07-30 00:39:44 (UTC)
Locking successful Project diggerhq/terragrunt-layers-example#layer2_analytics has been locked by PR #4
Error during init. 00:39:47.058 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 00:39:47.715 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. 00:39:48.283 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. 00:39:48.302 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.
00:39:49.350 ERROR Failed to execute "terraform output -json" in ../../layer1/monitoring/.terragrunt-cache/4077439280

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

@motatoes motatoes closed this Jul 30, 2025
@digger-app-1932760430
Copy link

👷 Digger starting....

@motatoes motatoes reopened this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status Plan + ~ -
layer1_storage succeeded Plan 0 0 0
layer2_frontend succeeded Plan 0 0 0
layer2_analytics succeeded Plan 0 0 0
layer2_api succeeded Plan 0 0 0

@motatoes motatoes closed this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

✅ Command unlock completed successfully

@motatoes motatoes reopened this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status Plan + ~ -
layer2_analytics succeeded Plan 0 0 0
layer2_api failed Plan 0 0 0
layer2_frontend succeeded Plan 0 0 0
layer1_storage succeeded Plan 0 0 0

@github-actions
Copy link

github-actions bot commented Jul 30, 2025

plan for layer2_api 2025-07-30 01:51:21 (UTC)
Locking successful Project diggerhq/terragrunt-layers-example#layer2_api has been locked by PR #4
Error during init. 01:51:24.475 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:51:25.035 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:51:25.567 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.

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:51:26.581 ERROR Failed to execute "terraform output -json" in ../../layer1/storage/.terragrunt-cache/2574979041

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

@motatoes motatoes closed this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

✅ Command unlock completed successfully

@motatoes motatoes reopened this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status
🕚 layer1_storage pending...
🕚 layer2_analytics pending...
🕚 layer2_api pending...
🕚 layer2_frontend pending...

@motatoes motatoes closed this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status Apply + ~ -
layer1_storage succeeded Apply 0 0 0

@github-actions
Copy link

github-actions bot commented Jul 30, 2025

apply for layer1_storage 2025-07-30 02:49:29 (UTC)
Locking successful Project diggerhq/terragrunt-layers-example#layer1_storage has been locked by PR #4
Apply output
No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Warning: Value for undeclared variable

The root module does not declare a variable named "region" but a value was
found in file
"/home/runner/work/terragrunt-layers-example/terragrunt-layers-example/layer1/storage/../../common.tfvars".
If you meant to use this value, add a "variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

bucket_names = [
  "terragrunt-example-development-bucket-1",
  "terragrunt-example-development-bucket-2",
  "terragrunt-example-development-bucket-3",
]
rds_endpoint = "3064820737195166467"
storage_config = {
  "bucket_names" = [
    "terragrunt-example-development-bucket-1",
    "terragrunt-example-development-bucket-2",
    "terragrunt-example-development-bucket-3",
  ]
  "rds_endpoint" = "3064820737195166467"
}

@motatoes motatoes closed this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

✅ Command unlock completed successfully

@motatoes motatoes reopened this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Layer
🕚 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
Copy link
Contributor Author

digger plan --layer 1

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status Plan + ~ -
layer1_storage succeeded Plan 0 0 0

@motatoes motatoes closed this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

✅ Command unlock completed successfully

@motatoes motatoes reopened this Jul 30, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Layer
🕚 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
Copy link
Contributor Author

digger plan --layer 1

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 30, 2025

Project Status Plan + ~ -
layer1_storage succeeded Plan 0 0 0

@motatoes motatoes closed this Jul 31, 2025
@motatoes motatoes reopened this Jul 31, 2025
@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 31, 2025

✅ Command unlock completed successfully

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 31, 2025

Project Layer
🕚 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
Copy link
Contributor Author

digger plan --layer 1

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 31, 2025

Project Status Plan + ~ -
layer1_storage succeeded Plan 0 0 0

@motatoes
Copy link
Contributor Author

digger plan

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 31, 2025

Project Status Plan + ~ -
layer1_storage succeeded Plan 0 0 0
layer2_api succeeded Plan 0 0 0
layer2_analytics failed Plan 0 0 0
layer2_frontend succeeded Plan 0 0 0

@motatoes
Copy link
Contributor Author

digger plan --layer 2

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 31, 2025

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

@motatoes
Copy link
Contributor Author

digger plan -p layer2_analytics

@digger-app-1932760430
Copy link

digger-app-1932760430 bot commented Jul 31, 2025

Project Status Plan + ~ -
layer2_analytics succeeded Plan 0 0 0

@github-actions
Copy link

plan for layer2_analytics 2025-07-31 05:01:49 (UTC)
Locking successful Project diggerhq/terragrunt-layers-example#layer2_analytics has been locked by PR #4

@github-actions
Copy link

github-actions bot commented Jul 31, 2025

plan for layer2_analytics 2025-07-31 05:02:12 (UTC)
Locking successful Project diggerhq/terragrunt-layers-example#layer2_analytics has been locked by PR #4
Error during init. 05:02:15.185 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 05:02:15.861 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. 05:02:16.244 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. 05:02:16.261 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.
05:02:17.306 ERROR Failed to execute "terraform output -json" in ../../layer1/compute/.terragrunt-cache/4284182190

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

@motatoes motatoes closed this Jul 31, 2025
@opentaco-cloud
Copy link

✅ Command unlock completed successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants