Merge branch '7.2' into 7.3

javiereguiluz · javiereguiluz · commit 19e4c7c184be · 2025-07-22T16:46:37.000+02:00
* 7.2:
  Minor reword
  Document how to resolve env var at compile time
diff --git a/components/dependency_injection/compilation.rst b/components/dependency_injection/compilation.rst
@@ -608,3 +608,25 @@ have the cache will be considered stale.
 
     In the full-stack framework the compilation and caching of the container
     is taken care of for you.
+
+.. _resolving-env-vars-at-compile-time:
+
+Resolving Environment Variable At Compile Time
+----------------------------------------------
+
+.. caution::
+
+    **This practice is discouraged**. Use it only if you fully understand the implications.
+
+By default, environment variables are resolved at runtime. However, you can
+force their resolution at compile time using the following code::
+
+    $parameterValue = $container->resolveEnvPlaceholders(
+        $container->getParameter('%env(ENV_VAR_NAME)%'),
+        true // resolve to actual values
+    );
+
+However, a **major drawback** of this approach is that you must manually clear
+the cache when changing the value of an environment variable. This goes
+against the typical behavior of environment variables, which are designed
+to be dynamic and not require cache invalidation.
diff --git a/configuration/env_var_processors.rst b/configuration/env_var_processors.rst
@@ -951,3 +951,9 @@ To enable the new processor in the app, register it as a service and
 tag. If you're using the
 :ref:`default services.yaml configuration <service-container-services-load-example>`,
 this is already done for you, thanks to :ref:`autoconfiguration <services-autoconfigure>`.
+
+Resolving Environment Variable At Compile Time
+----------------------------------------------
+
+Environment variables are resolved at runtime, but you can also resolve them
+:ref:`at compile time <resolving-env-vars-at-compile-time>`.
