feat/generate projects (#1968)

* set flag

* documenting the use of env variable

* Update docs/ce/howto/using-terragrunt.mdx

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>

---------

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>

Author: motatoes

docs/ce/howto/using-terragrunt.mdx

@@ -31,7 +31,10 @@ since this way may be deprecated in the future
 
 [Demo repo](https://github.com/diggerhq/test-terragrunt-racecondition)
 
-In many cases with terragrunt you don't want to mention all of your terragrunt components since there can be tens or hundreds of those (not to mention all the dependencies of those). In this case you can just leave it to digger and it will perform dynamic generation of projects for you before triggering the relevant `terragrunt apply` commands on all impacated projects per pull request. It will also handle dependencies of these projects. You can configure this using the following:
+In many cases with terragrunt you don't want to mention all of your terragrunt components since there can be tens or hundreds of those (not to mention all the dependencies of those). In this case you can just leave it to digger and it will perform dynamic generation of projects for you before triggering the relevant `terragrunt apply` commands on all impacted projects per pull request. It will also handle dependencies of these projects. You can configure this using the following:
+
+
+
 
 ```
 generate_projects:
@@ -66,3 +69,17 @@ jobs:
           setup-terragrunt: true
           terragrunt-version: 0.44.1
 ```
+
+### Note regarding SOPS
+
+Since currently the generation happens in the backend where no access to SOPS variables exist this means
+    that if you use sops_decrypt_file in your terragrunt.hcl it will lead to an exception of sops decryption failed.
+    Current workaround is to use environment variable `DIGGER_GENERATE_PROJECT` and check if its true as follows:
+
+```
+locals {
+  secrets = get_env("DIGGER_GENERATE_PROJECT", "false") == "true" ? {} : yamldecode(sops_decrypt_file("secrets.yaml"))
+}
+```
+
+This will ensure that an exception doesn't occur during generation in the backend.

libs/digger_config/digger_config.go

@@ -322,6 +322,8 @@ func checkBlockInChangedFiles(dir string, changedFiles []string) bool {
 }
 
 func HandleYamlProjectGeneration(config *DiggerConfigYaml, terraformDir string, changedFiles []string) error {
+	os.Setenv("DIGGER_GENERATE_PROJECT", "true")
+	defer os.Unsetenv("DIGGER_GENERATE_PROJECT")
 	if config.GenerateProjectsConfig != nil && config.GenerateProjectsConfig.TerragruntParsingConfig != nil {
 		slog.Warn("terragrunt generation using top level config is deprecated",
 			"recommendation", "https://docs.digger.dev/howto/generate-projects#blocks-syntax-with-terragrunt")