Allow using the security checker in all environments #402
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
deployed
to
wasbait
approved these changes
Apr 23, 2018
fabpot
approved these changes
Apr 23, 2018
sstok
approved these changes
Apr 23, 2018
xabbuh
approved these changes
Apr 23, 2018
ghost
pushed a commit
that referenced
this pull request
Apr 23, 2018
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We received an issue report in the Docs: symfony/symfony-docs#9612 of a user that installed the security checker but can't use it in their CI environment (
APP_ENV=CI).Is there any strong reason to only allow using this in the
devenvironment? I'd say you can/must use this critically important command even inprodenv.