Just started a new projec. Was about to remove the default token based authentication...

Was thrilled to see sanctum already setup! Love this ❤️

With this PR merged all our packages failed on integration for actingAs (eg $response = $this->actingAs($billable)->json('GET', 'api/payments/');) method tests with testbench throwing the error

InvalidArgumentException: Auth guard [api] is not defined.

Solution to that was to add api guard to config from boot method in package ServiceProvider eg

public function boot() {
        $config = $this->app->make('config');
        $config->set('auth.guards', array_merge(
            [
                'api' => [
                    'driver' => 'passport',
                    'provider' => 'users',
                ],
            ],
            $config->get('auth.guards', [])
        ));
}

I'm posting this since finding the solution at this time was impossible with searching issues/forums/etc.

@qunabu this is a starter skeleton package. You don't need to adopt changes made in existing apps. Just re-add the api guard to your auth config.

My comment refers only for Package Development and CI integration testing with testbench. The above is one possible solution, but you can also change this just for tests environment with

protected function getEnvironmentSetUp($app) {
    $app['config']->set('auth.guards.api', [
                    'driver' => 'passport',
                    'provider' => 'users',
                ]);
}

More context

I'm developing app with independent packages. If in you package you have in composer.json

"laravel/framework": "^8", or "laravel/framework": "^8.6",

and have been using api guard, code that used to work is no longer working because defaults laravel no longer have api guard as default. Integration API tests testbench is fetching one from composer, that's why you need to amend package code testing to be working.

With no change in code our CI/CD 2 days ago throwed an error
InvalidArgumentException: Auth guard [api] is not defined. for the code that used to work.

Like you @driesvints mentioned for the standard app development this is not a case at all, just packages.

PS. I'm going to change api guard with sanctum sooner then later

Hi @qunabu

I intentionally sync the Laravel changes and release them as breaking changes to ensure that every packages depending on api knows that starting from last week release new created Laravel app doesn't come with api auth guard.

What you need to do as a package developer:

1. My package explicitly use api

You need to update getEnvironmentSetUp($app) to re-set the configuration and inform potential users that they need to set auth.guards.api configuration manually.

2. api is only used for packages tests, it shouldn't affect end-user

You just need to update getEnvironmentSetup($app)

@qunabu I completely agree with you. We're facing the same problem and our packages CI/CD are failing for no reason.

@crynobone I think you are missing the point here. this change in this PR will only affect the new projects created by this skeleton. But your breaking change on a patch version on your package will affect existing projects completely out of the blue. This is not a professional move. I think you should adopt this change to the next major version of your package.

@crynobone

I intentionally sync the Laravel changes and release them as breaking changes to ensure that every packages depending on api knows that starting from last week release new created Laravel app doesn't come with api auth guard

I couldn't find this information can you point me out where is it.

Thanks for clarifying.