Unable to Run Interactive Artisan Commands from Laravel Migrations about framework

[adelynx]

@crynobone please do not close this ticket or convert it to a discussion because this is a genuine issue. @taylorotwell, could you please look into this? The team is closing it without any explanation.

[driesvints]

Since you're already operating in an artisan context, it's not really the place to run these. I suggest using calling the DB builder directly if you need to migrate data.

[adelynx]

@driesvints There are many scenarios where we need to run interactive commands within migrations; calling the Artisan command user:create is just one example to illustrate the issue. Additionally, it's important to note that using db:seed doesn't track which seeders have been executed, leading to a risk of duplicating seeders. Unlike migrations, which are tracked in the migrations table to log which migrations have already been applied, seeders lack this mechanism.

I think it's unfair to close the ticket without proper investigation or at least escalating it, as this is a genuine issue. Forcing a specific business rule on everyone isn't ideal. Honestly, this behaviour might push me away from using Laravel.

ping @taylorotwell

[driesvints]

I'm sorry but we don't support such a scenario. It was never intended to call artisan commands from migrations.

[adelynx]

I'm sorry but we don't support such a scenario. It was never intended to call artisan commands from migrations.

Well, then you are missing a lot.