Fixes #16331 - Don't make passport:install command require user input #16341
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.
At some point,
php artisan passport:install
started to require some level of user-input in order to function - and this isn't going to at all work well when it's being run viaArtisan::call()
- which is in a web-context. PHP docs explicitly mention thatSTDIN
is only defined when running in a command-line context, which we definitely are not doing in a web GUI context.This change just adds a
--no-interaction
flag to the Passport artisan command so it won't get hung up looking for user input onSTDIN
.I tested on my local on a blank database and this did, actually, seem to wwork.