Default settings applied on appsettings.json is not propagating when deployed as an ECS Task #8275

7 Answer(s)

• 

  0

  liangshiwei created one month ago

  Support Team Fullstack Developer

  Hi,

  you can override SettingProvider and SettingManagement to log the setting value from where and check it log.

  [Dependency(ReplaceServices = true)]
  [ExposeServices(typeof(ISettingProvider))]
  public class MySettingProvider : SettingProvider
  {
      private readonly ILogger<MySettingManagement> _logger;
      public MySettingProvider([NotNull] ISettingDefinitionManager settingDefinitionManager, [NotNull] ISettingEncryptionService settingEncryptionService, [NotNull] ISettingValueProviderManager settingValueProviderManager, ILogger<MySettingManagement> logger) : base(settingDefinitionManager, settingEncryptionService, settingValueProviderManager)
      {
          _logger = logger;
      }
  
      protected async override Task<string> GetOrNullValueFromProvidersAsync(IEnumerable<ISettingValueProvider> providers, SettingDefinition setting)
      {
          foreach (var provider in providers)
          {
              var value = await provider.GetOrNullAsync(setting);
              _logger.LogInformation($"Get value from SettingProvider: {provider.Name}, Value: {value}");
              if (value != null)
              {
                  return value;
              }
          }
  
          return null;
      }
  }
  
  [Dependency(ReplaceServices = true)]
  [ExposeServices(typeof(ISettingManager))]
  public class MySettingManagement : SettingManager
  {
      private readonly ILogger<MySettingManagement> _logger;
      public MySettingManagement(IOptions<SettingManagementOptions> options, IServiceProvider serviceProvider, ISettingDefinitionManager settingDefinitionManager, ISettingEncryptionService settingEncryptionService, ISettingManagementStore settingManagementStore, ILogger<MySettingManagement> logger) : base(options, serviceProvider, settingDefinitionManager, settingEncryptionService, settingManagementStore)
      {
          _logger = logger;
      }
  
      protected async override Task<string> GetOrNullInternalAsync(string name, string providerName, string providerKey, bool fallback = true)
      {
          var setting = await SettingDefinitionManager.GetAsync(name);
          var providers = Enumerable
              .Reverse(Providers);
  
          if (providerName != null)
          {
              providers = providers.SkipWhile(c => c.Name != providerName);
          }
  
          if (!fallback || !setting.IsInherited)
          {
              providers = providers.TakeWhile(c => c.Name == providerName);
          }
  
          string value = null;
          foreach (var provider in providers)
          {
              value = await provider.GetOrNullAsync(
                  setting,
                  provider.Name == providerName ? providerKey : null
              );
  
              _logger.LogInformation($"Get value from SettingProvider: {provider.Name}, Value: {value}");
              if (value != null)
              {
                  break;
              }
          }
  
          if (setting.IsEncrypted)
          {
              value = SettingEncryptionService.Decrypt(setting, value);
          }
  
          return value;
      }
  }
  

  Save Cancel
• 

  0

  Bryan-EDV created one month ago

  Will post the results here soon

  Save Cancel
• 

  0

  liangshiwei created one month ago

  Support Team Fullstack Developer

  okay

  Save Cancel
• 

  0

  Bryan-EDV created one month ago

  Hi managed to get it resolved. We realised that as part of our CI/CD pipeline, we were running dotnet publish "MyApp.sln"

  During the creation of artifacts, the last project to be published is NOT the HttpApi.Host project. Hence, appsettings.json for HttpApi.Host was overwritten by another project appsettings.json.

  The resolution was to only publish the needed artifact i.e. dotnet publish "MyApp.HttpApi.Host/MyApp.HttpApi.Host.csproj"

  Note: the commands are not exactly as used in our project but conveys the idea (we also added flags such as -c Release etc)

  Save Cancel
• 

  0

  Bryan-EDV created one month ago

  Also, do you happen to know the change you made in this ticket: https://abp.io/qa/questions/7297/3a130461-8b69-1a8a-743f-133fccbac906

  We are having the exact same issue whereby the issuer still defaults to the main domain of the backend (api.mydomain.com) instead of the subdomain (tenant.api.mydomain.com).

  Save Cancel
• 

  0

  liangshiwei created one month ago

  Support Team Fullstack Developer

  Hi,

  It's a new question.

  I think we close this. : )

  Save Cancel
• 

  0

  Bryan-EDV created one month ago

  thanks,

  fyi managed to solve new question issue by removing serverBuilder.SetIssuer(new Uri(configuration["AuthServer:Authority"]!));

  Save Cancel