InfisicalDotNet 1.0.1

There is a newer prerelease version of this package available.
See the version list below for details.
dotnet add package InfisicalDotNet --version 1.0.1
NuGet\Install-Package InfisicalDotNet -Version 1.0.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="InfisicalDotNet" Version="1.0.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add InfisicalDotNet --version 1.0.1
#r "nuget: InfisicalDotNet, 1.0.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install InfisicalDotNet as a Cake Addin
#addin nuget:?package=InfisicalDotNet&version=1.0.1

// Install InfisicalDotNet as a Cake Tool
#tool nuget:?package=InfisicalDotNet&version=1.0.1

InfisicalDotNet

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

Nuget

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, in which case it uses 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.

Why can't I specify the secret path, workspace or environment?

When you create a service token it is scoped to a specific workspace, environment and secret path, so this configuration provider uses those.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.1.0-alpha0032 80 2/4/2024
1.0.1 115 2/4/2024
1.0.1-alpha.26 44 2/4/2024
1.0.1-alpha.25 734 11/4/2023
1.0.1-alpha.23 61 11/4/2023
1.0.1-alpha.22 58 11/4/2023
1.0.1-alpha.20 60 11/3/2023
1.0.1-alpha.18 54 11/2/2023
1.0.1-alpha.15 53 11/2/2023
1.0.1-alpha.14 50 11/2/2023
1.0.1-alpha.12 55 11/2/2023
1.0.0-alpha.9 55 11/2/2023