Error when i set a custom website UUID

[Ohabiballah]

Every things works fine but when i add a specific $website->uuid it's give me this error : SQLSTATE[HY000] [1045] Access denied for user 'rmaroc.heyme-intermediation.local'@'localhost' (using password: YES) (SQL: select * from information_schema.tables where table_schema = rmaroc.heyme-intermediation.local and table_name = migrations and table_type = 'BASE TABLE')

the rmaroc.heyme-intermediation.local is the custom uuid that i set.

this is my tenancy config file : `
use Hyn\Tenancy\Database\Connection;

 return [
 /**
 * Random key used for tenant database user password
 */
 'key' => env('TENANCY_KEY', env('APP_KEY')),

'models' => [
    /**
     * Specify different models to be used for the global, system database
     * connection. These are also used in their relationships. Models
     * used have to implement their respective contracts and
     * either extend the SystemModel or use the trait
     * UsesSystemConnection.
     */

    // Must implement \Hyn\Tenancy\Contracts\Hostname
    'hostname' => \Hyn\Tenancy\Models\Hostname::class,

    // Must implement \Hyn\Tenancy\Contracts\Website
    'website' => \Hyn\Tenancy\Models\Website::class
],
/**
 * The package middleware. Removing a middleware here will disable it.
 * You can of course extend/replace them or add your own.
 */
'middleware' => [
    // The eager identification middleware.
    \Hyn\Tenancy\Middleware\EagerIdentification::class,

    // The hostname actions middleware (redirects, https, maintenance).
    \Hyn\Tenancy\Middleware\HostnameActions::class,
],
'website' => [
    /**
     * Each website has a short random hash that identifies this entity
     * to the application. By default this id is randomized and fully
     * auto-generated. In case you want to force your own logic for
     * when you need to have a better overview of the complete
     * tenant folder structure, disable this and implement
     * your own id generation logic.
     */
    'disable-random-id' => false,

    /**
     * The random Id generator is responsible for creating the hash as mentioned
     * above. You can override what generator to use by modifying this value
     * in the configuration.
     *
     * @warn This won't work if disable-random-id is true.
     */
    'random-id-generator' => Hyn\Tenancy\Generators\Uuid\ShaGenerator::class,

    /**
     * Enable this flag in case you're using a driver that does not support
     * database username or database name with a length of more than 32 characters.
     *
     * This should be enabled for MySQL, but not for MariaDB and PostgreSQL.
     */
    'uuid-limit-length-to-32' => env('LIMIT_UUID_LENGTH_32', false),

    /**
     * Specify the disk you configured in the filesystems.php file where to store
     * the tenant specific files, including media, packages, routes and other
     * files for this particular website.
     *
     * @info If not set, will revert to the default filesystem.
     * @info If set to false will disable all tenant specific filesystem auto magic
     *       like the config, vendor overrides.
     */
    'disk' => 'local',

    /**
     * Automatically generate a tenant directory based on the random id of the
     * website. Uses the above disk to store files to override system-wide
     * files.
     *
     * @info set to false to disable.
     */
    'auto-create-tenant-directory' => true,

    /**
     * Automatically rename the tenant directory when the random id of the
     * website changes. This should not be too common, but in case it happens
     * we automatically want to move files accordingly.
     *
     * @info set to false to disable.
     */
    'auto-rename-tenant-directory' => true,

    /**
     * Automatically deletes the tenant specific directory and all files
     * contained within.
     *
     * @see
     * @info set to true to enable.
     */
    'auto-delete-tenant-directory' => false,

    /**
     * Time to cache websites in minutes. Set to false to disable.
     */
    'cache' => 10,
],
'hostname' => [
    /**
     * If you want the multi tenant application to fall back to a default
     * hostname/website in case the requested hostname was not found
     * in the database, complete in detail the default hostname.
     *
     * @warn this must be a FQDN, these have no protocol or path!
     */
    'default' => env('TENANCY_DEFAULT_HOSTNAME'),
    /**
     * The package is able to identify the requested hostname by itself,
     * disable to get full control (and responsibility) over hostname
     * identification. The hostname identification is needed to
     * set a specific website as currently active.
     *
     * @see src/Jobs/HostnameIdentification.php
     */
    'auto-identification' => env('TENANCY_AUTO_HOSTNAME_IDENTIFICATION', true),

    /**
     * In case you want to have the tenancy environment set up early,
     * enable this flag. This will run the tenant identification
     * inside a middleware. This will eager load tenancy.
     *
     * A good use case is when you have set "tenant" as the default
     * database connection.
     */
    'early-identification' => env('TENANCY_EARLY_IDENTIFICATION', true),

    /**
     * Abort application execution in case no hostname was identified. This will throw a
     * 404 not found in case the tenant hostname was not resolved.
     */
    'abort-without-identified-hostname' => env('TENANCY_ABORT_WITHOUT_HOSTNAME', false),

    /**
     * Time to cache hostnames in minutes. Set to false to disable.
     */
    'cache' => 10,

    /**
     * Automatically update the app.url configured inside Laravel to match
     * the tenant FQDN whenever a hostname/tenant was identified.
     *
     * This will resolve issues with password reset mails etc using the
     * correct domain.
     */
    'update-app-url' => false,
],
'db' => [
    /**
     * The default connection to use; this overrules the Laravel database.default
     * configuration setting. In Laravel this is normally configured to 'mysql'.
     * You can set a environment variable to override the default database
     * connection to - for instance - the tenant connection 'tenant'.
     */
    'default' => env('TENANCY_DEFAULT_CONNECTION'),
    /**
     * Used to give names to the system and tenant database connections. By
     * default we configure 'system' and 'tenant'. The tenant connection
     * is set up automatically by this package.
     *
     * @see src/Database/Connection.php
     * @var system-connection-name The database connection name to use for the global/system database.
     * @var tenant-connection-name The database connection name to use for the tenant database.
     */
    'system-connection-name' => env('TENANCY_SYSTEM_CONNECTION_NAME', Connection::DEFAULT_SYSTEM_NAME),
    'tenant-connection-name' => env('TENANCY_TENANT_CONNECTION_NAME', Connection::DEFAULT_TENANT_NAME),

    /**
     * The tenant division mode specifies to what database websites will be
     * connecting. The default setup is to use a new database per tenant.
     * If using PostgreSQL, a new schema per tenant in the same database can
     * be setup, by optionally setting division mode to 'schema'.
     * In case you prefer to use the same database with a table prefix,
     * set the mode to 'prefix'.
     * To implement a custom division mode, set this to 'bypass'.
     *
     * @see src/Database/Connection.php
     */
    'tenant-division-mode' => env('TENANCY_DATABASE_DIVISION_MODE', 'database'),

    /**
     * The database password generator takes care of creating a valid hashed
     * string used for tenants to connect to the specific database. Do
     * note that this will only work in 'division modes' that set up
     * a connection to a separate database.
     */
    'password-generator' => Hyn\Tenancy\Generators\Database\DefaultPasswordGenerator::class,

    /**
     * The tenant migrations to be run during creation of a tenant. Specify a directory
     * to run the migrations from. If specified these migrations will be executed
     * whenever a new tenant is created.
     *
     * @info set to false to disable auto migrating.
     *
     * @warn this has to be an absolute path, feel free to use helper methods like
     * base_path() or database_path() to set this up.
     */
    'tenant-migrations-path' => database_path('migrations/tenant'),

    /**
     * The default Seeder class used on newly created databases and while
     * running artisan commands that fire seeding.
     *
     * @info requires tenant-migrations-path in order to seed newly created websites.
     * @info seeds stored in `database/seeds/tenants` need to be configured in your composer.json classmap.
     *
     * @warn specify a valid fully qualified class name.
     */
    'tenant-seed-class' => TenantDatabaseSeeder::class,

// eg an admin seeder under app/Seeders/AdminSeeder.php: // 'tenant-seed-class' => App\Seeders\AdminSeeder::class,

    /**
     * Automatically generate a tenant database based on the random id of the
     * website.
     *
     * @info set to false to disable.
     */
    'auto-create-tenant-database' => true,

    /**
     * Automatically generate the user needed to access the database.
     *
     * @info Useful in case you use root or another predefined user to access the
     *       tenant database.
     * @info Only creates in case tenant databases are set to be created.
     *
     * @info set to false to disable.
     */
    'auto-create-tenant-database-user' => true,

    /**
     * Set of database privileges to give to the tenant database user.
     *
     * @info Useful in case your database restricts the privileges you
     *       can set (for example AWS RDS).
     * @info These privileges are only used in case tenant database users
     *       are set to be created.
     *
     * @info null by default means "ALL PRIVILEGES". Override with a list
     *       of privileges as a string, e.g. 'SELECT, UPDATE'.
     */
    'tenant-database-user-privileges' => null,

    /**
     * Automatically rename the tenant database when the random id of the
     * website changes. This should not be too common, but in case it happens
     * we automatically want to move databases accordingly.
     *
     * @info set to false to disable.
     */
    'auto-rename-tenant-database' => true,

    /**
     * Automatically deletes the tenant specific database and all data
     * contained within.
     *
     * @info set to true to enable.
     */
    'auto-delete-tenant-database' => env('TENANCY_DATABASE_AUTO_DELETE', false),

    /**
     * Automatically delete the user needed to access the tenant database.
     *
     * @info Set to false to disable.
     * @info Only deletes in case tenant database is set to be deleted.
     */
    'auto-delete-tenant-database-user' => env('TENANCY_DATABASE_AUTO_DELETE_USER', false),

    /**
     * Define a list of classes that you wish to force onto the tenant or system connection.
     * The connection will be forced when the Model has booted.
     *
     * @info Useful for overriding the connection of third party packages.
     */
    'force-tenant-connection-of-models' => [

// App\User::class ], 'force-system-connection-of-models' => [ // App\User::class ], ],

/**
 * Global tenant specific routes.
 * Making it easier to distinguish between landing and tenant routing.
 *
 * @info only works with `tenancy.hostname.auto-identification` or identification happening
 *       before the application is booted (eg inside middleware or the register method of
 *       service providers).
 */
'routes' => [
    /**
     * Routes file to load whenever a tenant was identified.
     *
     * @info Set to false or null to disable.
     */
    'path' => base_path('routes/tenants.php'),

    /**
     * Set to true to flush all global routes before setting the routes from the
     * tenants.php routes file.
     */
    'replace-global' => false,
],

/**
 * Folders configuration specific per tenant.
 * The following section relates to configuration to files inside the tenancy/<uuid>
 * tenant directory.
 */
'folders' => [
    'config' => [
        /**
         * Merge configuration files from the config directory
         * inside the tenant directory with the global configuration files.
         */
        'enabled' => true,

        /**
         * List of configuration files to ignore, preventing override of crucial
         * application configurations.
         */
        'blacklist' => ['database', 'tenancy', 'webserver'],
    ],
    'routes' => [
        /**
         * Allows adding and overriding URL routes inside the tenant directory.
         */
        'enabled' => true,

        /**
         * Prefix all tenant routes.
         */
        'prefix' => null,
    ],
    'trans' => [
        /**
         * Allows reading translation files from a trans directory inside
         * the tenant directory.
         */
        'enabled' => true,

        /**
         * Will override the global translations with the tenant translations.
         * This is done by overriding the laravel default translator with the new path.
         */
        'override-global' => true,

        /**
         * In case you disabled global override, specify a namespace here to load the
         * tenant translation files with.
         */
        'namespace' => 'tenant',
    ],
    'vendor' => [
        /**
         * Allows using a custom vendor (composer driven) folder inside
         * the tenant directory.
         */
        'enabled' => true,
    ],
    'media' => [
        /**
         * Mounts the assets directory with (static) files for public use.
         */
        'enabled' => true,
    ],
    'views' => [
        /**
         * Enables reading views from tenant directories.
         */
        'enabled' => true,

        /**
         * Specify a namespace to use with which to load the views.
         *
         * @eg setting `tenant` will allow you to use `tenant::some.blade.php`
         * @info set to null to add to the global namespace.
         */
        'namespace' => null,

        /**
         * If `namespace` is set to null (thus using the global namespace)
         * make it override the global views. Disable by setting to false.
         */
        'override-global' => true,
    ]
]

]; ` this is the first time i use tenancy please can you help me .

[Ohabiballah]

I did a lot of tests, the problem is when I use a uuid for the first time it's work fine so when i delete this tenant and use the same uuid for the second time it's show this problem.

[Bibendus83]

When you delete the database do you remember to delete the associated user too? If you don't and use the same uuid probably the user remains created with the old password and you can't access to the new database. If I remember correctly there is a create user if not exists query during the database creation that will not throw an error if a user with the same name is found. IMO an error should be thrown to identify such kind of problems.

[fletch3555]

@Bibendus83 is most likely correct. When you delete a tenant, make sure you use the WebsiteRepository as it will fire the necessary events to cleanup the extras such as the database user.