How can I change a setting in appsettings.json after auto-deploy?

Question

I have an ASP.NET Core application going on an have setup Github auto-deploy on it. But since it's an open repo I obviously don't want to upload my correct configuration file.

What I'd like to do is to replace some strings in the appsettings.json after a github auto deploy.

"AppSettings": {
    "Token": "my super duper secret token"
}

How can I change my super duper secret token to my real token after a github deploy on Azure?

Answer 1

As I know we can config token in App Settings on the Azure port. I do a test on this, it works successfully, the following is my detail steps.

1. Create an Asp.net core Application.
2. Add [AppSettings] section in the appsetting.json file (Token vaule: mysecretkey).
3. Add a public class AppSettings.cs under the created project.
4. Add the code services.Configure<AppSettings>(Configuration.GetSection("AppSettings")) in the function ConfigureService function in the Startup.cs file (For .net Core 1.0).

Note:The syntax for model binding has changed from RC1 to RC2. Using services.Configure<AppSettings>(Configuration.GetSection("AppSettings")), is no longer availableIn order to bind a settings class to your configuration you need to configure this in the ConfigureServices method of Startup.cs: services.Configure<AppSettings>(options => Configuration.GetSection("AppSettings").Bind(options));

5. Add code to the HomeController.cs file.

6. Publish the WebApp to the Azure Portal.
7. Add [AppSettings: Token] in the Azure Portal.
8. Browse the WebApp and select the about tab to see the token value is that the value set in the portal.

Answer 2

Assuming the web site already exists as a resource in Azure, you can simply set the App Settings/Connection strings in the portal. These will override the ones in the appsettings.json file at runtime. Ie. your app will first look at the azure app settings/connection strings before looking for them in the local file. This is part of asp.net core's "cloud first" approach to configuration management. These settings wont get overwritten when you deploy code to the app/slot.

Found a blog post here which describes it in a bit more detail, using the .AddEnvironmentVariables() call to add azure slot settings to the configuration.