search

aspnet / MicrosoftConfigurationBuilders

Microsoft.Configuration.Builders
MIT License
118 stars 61 forks source link

Azure WebJobs/environment variables workaround inadequate #225

Open jfitch11 opened 1 year ago

jfitch11 commented 1 year ago

I've run into this issue using 3.0 of the package and the workaround doesn't seem adequate for SQL Connection strings that use the app service environment variables

https://github.com/aspnet/MicrosoftConfigurationBuilders/issues/133

When following the example and setting the EnvironmentConfigBuilder to pull inSQLAZURECONNSTR_ it drops the providerName attribute in the connection string and (at least for my app) errors. Would strict mode and renaming the connection strings prevent providerName from being dropped?

Additionally is there an item for this issue with the Azure App Service Team (since web apps work fine)?

jfitch11 commented 1 year ago

Using ConnectionStringsSectionHandler2 along with the workaround appears to work here.

ojintoad commented 1 year ago

Howdy - we did work around the first item which is great.

Is there an answer for the second concern?

Additionally is there an item for this issue with the Azure App Service Team (since web apps work fine)?

This is referring to:

This is probably something that should get filed with the Azure App Services team. There's really no reason why the presence of an attribute should throw off their pre-runtime xml injection. Or maybe there is good reason, but I'm not part of the team that would know. Anyway...

In this comment: https://github.com/aspnet/MicrosoftConfigurationBuilders/issues/133#issuecomment-1049520479

I'm not sure where we would file this on our end, it does seem like something someone within Microsoft would understand better how to accomplish or at least might be able to guide us on doing. Happy to help!