I found a migration problem related to our use case and Features::twoFactorAuthentication.
We want to use 2FA but not yet, so we install jetpack with livewire support and no teams, add the migrations to our git repository, and disallow 2FA at fortify.php, that's required because we don't want our users to use 2FA yet, then we create a new migration to add our admin users.
Here, we have:
jetpack installed
jetpack migrations added on our migrations directory
default admin user added
Now, when other colleague try to start working on their computer, founds an error like:
That's because on 2014_10_12_200000_add_two_factor_columns_to_users_table.php migration class we have:
if (Fortify::confirmsTwoFactorAuthentication()) {
$table->timestamp('two_factor_confirmed_at')
->after('two_factor_recovery_codes')
->nullable();
}
and, as 2FA is off, this field are not create.
I think that migrations should not have conditionals on it, specially when it's related to features that you can activate or deactivate on demand.
Simple solution will be remove that conditional check on jetpack migration
Steps To Reproduce:
Install laravel and jetpack
Comment/disallow Features::twoFactorAuthentication on fortify.php
Add a new migration to add one user
commit changes
try to install from commited repo (as on a new PC)
Description:
I found a migration problem related to our use case and Features::twoFactorAuthentication. We want to use 2FA but not yet, so we install jetpack with livewire support and no teams, add the migrations to our git repository, and disallow 2FA at fortify.php, that's required because we don't want our users to use 2FA yet, then we create a new migration to add our admin users.
Here, we have:
Now, when other colleague try to start working on their computer, founds an error like:
That's because on 2014_10_12_200000_add_two_factor_columns_to_users_table.php migration class we have:
and, as 2FA is off, this field are not create. I think that migrations should not have conditionals on it, specially when it's related to features that you can activate or deactivate on demand.
Simple solution will be remove that conditional check on jetpack migration
Steps To Reproduce: