From fdda76fe73d83158eba51bbff5798ddd38ccf1ef Mon Sep 17 00:00:00 2001
From: Javier Eguiluz <javier.eguiluz@gmail.com>
Date: Thu, 19 Sep 2024 12:41:59 +0200
Subject: [PATCH] [FrameworkBundle] Document the `resolve-env-vars` option of
 `lint:container` command

---
 service_container.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/service_container.rst b/service_container.rst
index 9e1cdff2098..f329587eb54 100644
--- a/service_container.rst
+++ b/service_container.rst
@@ -1069,6 +1069,14 @@ application to production (e.g. in your continuous integration server):
 
     $ php bin/console lint:container
 
+    # optionally, you can force the resolution of environment variables;
+    # the command will fail if any of those environment variables are missing
+    $ php bin/console lint:container --resolve-env-vars
+
+.. versionadded:: 7.2
+
+    The ``--resolve-env-vars`` option was introduced in Symfony 7.2.
+
 Performing those checks whenever the container is compiled can hurt performance.
 That's why they are implemented in :doc:`compiler passes </service_container/compiler_passes>`
 called ``CheckTypeDeclarationsPass`` and ``CheckAliasValidityPass``, which are