Resolve Env Vars when Linting the Container

The lint:container command runs some checks to validate the service container configuration.
However, it doesn’t check if all the environment variables used in your services are defined.

For example, if you define an env var for some environment (e.g. dev or staging)
but forget to define it in production, you’ll see an exception when the application
is already deployed. In Symfony 7.2 we’re adding the following option so you can
check that all the required env vars are also defined:

Messenger Stats in Different Formats

The messenger:stats command displays information about the number of
queued messages per transport. Unlike other Symfony commands, it doesn’t
provide its output in different formats. In 7.2, we improved this command to add
support for json and text formats:

Better Exit Code when Decrypting Secrets

The secrets:decrypt-to-local command decrypts all the Symfony secrets
and stores them in the local vault. However, when decryption fails for any reason
(e.g. you didn’t set an env var for the decryption key), the command prints some
error messages but exists with a successful status code.

In Symfony 7.2, when the command fails for any reason, the exist status will be
1 so you can detect that error and handle it correctly.

Allow to Skip Failed Messages

The messenger:failed:retry command allows you to view and retry failed messages.
For each message, it provides two options: either retry it right now or delete it.
However, sometimes you know you don’t want to delete it but aren’t sure about
retrying it right away.

That’s why in Symfony 7.2 you’ll see a third option: skip it for now, so you
can later decide what to do with it.

Asset Debugging Filters

The debug:asset-map command allows you to display detailed information about
your AssetMapper paths, namespace prefixes, logical paths, etc. As your application
grows, the output of this command becomes less manageable. That’s why in Symfony 7.2
we’ve introduced some options to filter results: