Contents
How to manage config files for multiple environments?
At first, the problem arises when you start thinking how you’re going to manage the basic config parameters of your app or service, like a port number, a database connection string or your Consul DNS — I mean you can’t hardcode them! Okay, there are ways to solve that (config files, etc.).
How to set aspnetcore _ environment variable in web.config?
To set the ASPNETCORE_ENVIRONMENT environment variable with web.config, see the Setting environment variables section of ASP.NET Core Module. Project file or publish profile. For Windows IIS deployments: Include the property in the publish profile (.pubxml) or project file.
Is it possible to set up ASP.NET Core 2.0 to always use HTTPS?
With a little bit of work you can setup your ASP.NET Core 2.0 site to always use HTTPS. In our next release we are working to simplify setting up HTTPS for ASP.NET Core apps and we plan to enable HTTPS in the project templates by default. We will share more details on these improvements as they become publicly available.
How is a config service deployed in a container?
Config service can be deployed as a container in stand-along node/machine or in Kubernetes cluster. Configuration data retrieved by the means of API, in the form of key-value pares. For example, an application, to retrieve the Cassandra database port number, would make a REST call similar to
Can a deployment have more than one environment?
This problem is applicable to any deployment with more than 1 environment in the picture, like DEV, QA, STG, PROD and so on. And the problem is, as you probably have guessed, the configuration data and its management.
What’s the best way to manage configuration data?
To sum it all up, we have identified the need for configuration data: have a single version of the truth. have a precise record of changes, along with a reference to what triggered the change (in other words, the audit trail). implement separation of concerns i.e. applications should be busy implementing business logic, and not managing configs.
Which is the best architecture for a config service?
By design, config service has pluggable architecture — we can plug it to any backend, like Consul, Cassandra or Git-compatible. It makes easy integration with a secrets management backend, like HashiCorp Vault, Azure Key Vault and AWS KMS. High-level sketch of config service architecture.