Open raymens opened 4 years ago
I've heard about this. Out of curiosity, where is the overlap between this and, say, keyvault?
It is a similar principle but built more for non-secret configuration. It also allows you to label specific settings so that you can adjust configuration on the fly for specific services, environments or whatever label you can think of or just use a single configuration set for multiple services and only adjust it once for all.
The configuration is loaded dynamically and thus there is no server restart like with the app settings of Web Apps.
You can also link to Key Vault items in the case of certificates and secrets etc. In that sense it is sort of an abstraction or pass through. So together they are a complete solution for settings and secret management.
Another interesting thing is that it supports setting feature flags for your app, where you can enable them according to various (also custom made) settings. Like for user X or Client Y, including a percentage of users etc.
It has SDKs to easily integrate this into asp.net core.
I've only just started looking into it and integrating it. But it looks promising.
Sounds promising. We need to think carefully about how to enable it through webapps and functions - one of the key drivers of Farmer is creating an easy-to-use abstraction for users without them needing to know the difference between all these services.
We would love the ability to add an Azure App Configuration to our existing Farmer template. I may attempt a PR of my own for this feature if there aren't any active plans for this.
Any update on this?
https://docs.microsoft.com/en-us/azure/azure-app-configuration/
The ARM template is quite terse, but it's perhaps handy to have it when it's part of a deployment.