English spoken conference
Talks Workshops Register
  1. Home
  2. Documentation
  3. Console
  4. How to Define Commands as Services
WARNING: You are browsing the documentation for Symfony 3.3 which is not maintained anymore. Consider upgrading your projects to Symfony 4.3.

How to Define Commands as Services

3.3 version
Maintained
3.4 4.3 current 4.4 5.0 master
Unmaintained
2.7 2.8 3.0 3.1 3.2 4.0 4.1 4.2

How to Define Commands as ServicesΒΆ

If you're using the default services.yml configuration, your command classes are already registered as services. Great! This is the recommended setup, but it's not required. Symfony also looks in the Command/ directory of each bundle and automatically registers those classes as commands.

Note

You can also manually register your command as a service by configuring the service and tagging it with console.command.

In either case, if your class extends ContainerAwareCommand, you can access public services via $this->getContainer()->get('SERVICE_ID').

But if your class is registered as a service, you can instead access services by using normal dependency injection.

For example, suppose you want to log something from within your command:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
namespace AppBundle\Command;

use Psr\Log\LoggerInterface;
use Symfony\Component\Console\Command\Command;
use Symfony\Component\Console\Input\InputInterface;
use Symfony\Component\Console\Output\OutputInterface;

class SunshineCommand extends Command
{
    private $logger;

    public function __construct(LoggerInterface $logger)
    {
        $this->logger = $logger;

        // you *must* call the parent constructor
        parent::__construct();
    }

    protected function configure()
    {
        $this
            ->setName('app:sunshine')
            ->setDescription('Good morning!');
    }

    protected function execute(InputInterface $input, OutputInterface $output)
    {
        $this->logger->info('Waking up the sun');
        // ...
    }
}

If you're using the default services.yml configuration, the command class will automatically be registered as a service and passed the $logger argument (thanks to autowiring). In other words, just by creating this class, everything works! You can call the app:sunshine command and start logging.

Caution

You do have access to services in configure(). However, try to avoid doing any work (e.g. making database queries), as that code will be run, even if you're using the console to execute a different command.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.