Now that we are a couple versions out from the migration of provisiond config into the database, when spinning up a new instance, especially a container, it can fail if the provisiond-configuration.xml file is missing. Can we provide some handling for assuming a default config state if the file is missing due to initializing the database off an existing config set that already has that file removed?