@maliming, We do that as a workaround for now, but it would be better to have the those setting names from the framework itself because want to keep code (.cs and appsetting.json files) to be similar to the orginal version as much as possible for ease of code merging when doing upgrading.
1. Key Vault
We put some credentials in Azure Key Vault and integrate with settings in the appsettting.json. The secret names are set in following pattern for hirachycal settings.
Unfortunately, they do not support setting name with periods (".").
2. Azure App Service Configuration
Normally, Azure App Service allow to override settings via app configuraiton. However, for App Service for Container we cannot do that if the setting name consist of periods (".").
@liangshiwei and @alper,
Sorry, It was my fault that I call method InitiliaseTenantDatabaseAsync(tenant) inside a non-awaitable method. That make the LifttimeScope end before all statements finish and throw the error.
I just change the method to be awaitable and the error gone.
Thank you for your promptly support, however.
@alper No I'm not trying to return entity to presentation layer, these codes are inside event handler to migrate database after provisioned resources dinamically.
@liangshiwei I use RabbitMq. Sorry that you cannot reproduced the error.
I have found the solution. I must add MwpApplicationContractsModule as a DependsOn module of MwpDbMigratorModule.
