InfisicalDotNet 1.0.1-alpha.18

InfisicalDotNet

This is a .NET library that makes it easy to use the .NET configuration system with Infisical.

How do I use this?

Install the package:

dotnet add package InfisicalDotNet

Set up the configuration provider:

using InfisicalDotNet;

var builder = WebApplication.CreateBuilder(args);

builder.Configuration
    .SetBasePath(builder.Environment.ContentRootPath)
    .AddInfisical(Environment.GetEnvironmentVariable("INFISICAL_SERVICE_TOKEN"));

// Add services to the container.

Or you can avoid specifying the service token, which grabs it from the INFISICAL_SERVICE_TOKEN environment variable behind the scenes:

using InfisicalDotNet;

var builder = WebApplication.CreateBuilder(args);

builder.Configuration
    .SetBasePath(builder.Environment.ContentRootPath)
    .AddInfisical();

// Add services to the container.

How do I format secret keys?

Secret keys should be formatted like environment variables. For example, consider this appsettings.json file:

{
  "ConnectionStrings": {
    "DefaultConnection": "Data Source=db.sqlite3"
  }
}

The equivalent of this JSON would be a secret in Infisical with the key CONNNECTIONSTRINGS__DEFAULTCONNECTION. Note the double underscore. More information on this is available in ASP.NET Core's environment variable naming documentation.

Possible future work

Currently this library only supports authentication using service tokens. Infisical service tokens are only allowed to access a specific workspace and environment. That is how this library knows which workspace and environment to use. It may be helpful eventually to support specifying the workspace and environment in addition to the service token and deriving the environment from the ASP.NET Core environment, in order to catch problems where the wrong Infisical service is specified for the ASP.NET Core environment.