-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The optional:true parameter for AddAzureAppConfiguration does not work #136
Comments
@zhenlan It looks like the |
The fix for this issue has been merged as a part of pull request #137. |
The fix has been released as a part of the version |
Are you sure it's fixed? I have the same problem as reported by @zhenlan with 3.0.1 return new ConfigurationBuilder() |
@eetawil Thanks for reporting it. You're right, the change fixed the issue for other exceptions, but not for the |
@abhilasharora I had hoped that this would cover our use case, which is ignoring only configuration values from keyvault that are inaccessible (e.g. due to no access permissions), instead of ignoring all configuration values if one can't be loaded from keyvault. Basically, we have hooked up multiple keyvaults in one app configuration, but not all apps have access to all keyvaults that are referenced there. So right now we can't load any configuration if we don't allow access to all keyvaults from all our apps. In preview version 2, I could still create a custom keyvault delegating handler that ignores 401, 403 and 404 errors and return an empty string, but I also can't seem to find this option anymore in version 4. Is there any way to support this use case? |
@b10-dslappendel Thanks for your feedback. This issue tracks the ability to use |
I have code below and a key vault reference in the store.
The app does not have access to my key vault, but since I specified
optional:true
, the app is not expected to throw. However, it does:The text was updated successfully, but these errors were encountered: