Prevent Autosetup from running if there is already a site.

[tcobbfis]

Currently, in our CI/CD setup, when I use autosetup I get the error "the provided database, table prefix and schema are already in use". I assume that when harness applies the new image to my aks cluster, it attempts the run the autosetup process even though it already ran during the initial setup of the instance.

[hishamco]

AutoSetup simply as names suggest creates a setup on your behalf, so an exception will be thrown if the database does not exist or the tables are already there. Cleaning the old database might be risky IMHO

[tcobbfis]

I get that, but the CI/CD process creates a new docker image with each change to the app. When this image is applied to the kubernetes cluster, it triggers the setup process regardless of whether or not there is a site already running.

It seems like the solution would be to use autosetup for the initial build, then remove it from the code (awkward but doable)

After trying this, I've realized that each build sends me to the startup form. The only way around is to reset the db.

Resetting the db with each build is not a solution for me, because there will be several different designers building and maintaining themes and tenants.

[tcobbfis]

Is there a way through code to have it target a site that is already in the database? And not just go under the assumption that there is no site already there.

[Piedone]

Auto Setup will not run if the site is already set up. It detects this by checking if the current tenant's shell settings indicate that the tenant is uninitialized.

From your error, it seems that while the DB remains there between startups, the shell settings store is wiped. Thus, Auto Setup thinks the tenant is uninitialized, tries to set it up, then fails on the DB existing.

So, you either need to wipe the DB as well, or configure shell settings to be stored in a durable manner. This can happen by putting the App_Data folder in a location that isn't reset (also see https://docs.orchardcore.net/en/latest/reference/modules/Configuration/#orchard_app_data-environment-variable) or storing it in the DB too (https://docs.orchardcore.net/en/latest/reference/modules/Shells/#database-shells-configuration-provider).