Merge branch '5.0'

* 5.0:
  [DI] Improve an example about automatic tags and bundles
  Remove webserver bundle usage
  Remove references to the secret env processors

Author: javiereguiluz

configuration/secrets.rst

@@ -111,7 +111,7 @@ If you stored a ``DATABASE_PASSWORD`` secret, you can reference by:
         # config/packages/doctrine.yaml
         doctrine:
             dbal:
-                password: '%env(secret:DATABASE_PASSWORD)%'
+                password: '%env(DATABASE_PASSWORD)%'
                 # ...
             # ...
 
@@ -129,7 +129,7 @@ If you stored a ``DATABASE_PASSWORD`` secret, you can reference by:
 
             <doctrine:config>
                 <doctrine:dbal
-                    password="%env(secret:DATABASE_PASSWORD)%"
+                    password="%env(DATABASE_PASSWORD)%"
                 />
             </doctrine:config>
 
@@ -140,7 +140,7 @@ If you stored a ``DATABASE_PASSWORD`` secret, you can reference by:
         // config/packages/doctrine.php
         $container->loadFromExtension('doctrine', [
             'dbal' => [
-                'password' => '%env(secret:DATABASE_PASSWORD)%',
+                'password' => '%env(DATABASE_PASSWORD)%',
             ]
         ]);
 

contributing/code/reproducer.rst

@@ -65,8 +65,9 @@ to a route definition. Then, after creating your project:
    of controllers, actions, etc. as in your original application.
 #. Create a small controller and add your routing definition that shows the bug.
 #. Don't create or modify any other file.
-#. Execute ``composer require symfony/web-server-bundle`` and use the ``server:run``
-   command to browse to the new route and see if the bug appears or not.
+#. Install the :doc:`local web server </setup/symfony_server>` provided by Symfony
+   and use the ``symfony server:start`` command to browse to the new route and
+   see if the bug appears or not.
 #. If you can see the bug, you're done and you can already share the code with us.
 #. If you can't see the bug, you must keep making small changes. For example, if
    your original route was defined using XML, forget about the previous route

service_container/tags.rst

@@ -117,8 +117,9 @@ If you want to apply tags automatically for your own services, use the
 
 
 For more advanced needs, you can define the automatic tags using the
-:method:`Symfony\\Component\\DependencyInjection\\ContainerBuilder::registerForAutoconfiguration`
-method in an :doc:`extension </bundles/extension>` or from your kernel::
+:method:`Symfony\\Component\\DependencyInjection\\ContainerBuilder::registerForAutoconfiguration` method.
+
+In a Symfony application, call this method in your kernel class::
 
     // src/Kernel.php
     class Kernel extends BaseKernel
@@ -133,6 +134,22 @@ method in an :doc:`extension </bundles/extension>` or from your kernel::
         }
     }
 
+In a Symfony bundle, call this method in the ``load()`` method of the
+:doc:`bundle extension class </bundles/extension>`::
+
+    // src/DependencyInjection/MyBundleExtension.php
+    class MyBundleExtension extends Extension
+    {
+        // ...
+
+        public function load(array $configs, ContainerBuilder $container)
+        {
+            $container->registerForAutoconfiguration(CustomInterface::class)
+                ->addTag('app.custom_tag')
+            ;
+        }
+    }
+
 Creating custom Tags
 --------------------