InfisicalDotNet 1.0.1
See the version list below for details.
dotnet add package InfisicalDotNet --version 1.0.1
NuGet\Install-Package InfisicalDotNet -Version 1.0.1
<PackageReference Include="InfisicalDotNet" Version="1.0.1" />
<PackageVersion Include="InfisicalDotNet" Version="1.0.1" />
<PackageReference Include="InfisicalDotNet" />
paket add InfisicalDotNet --version 1.0.1
#r "nuget: InfisicalDotNet, 1.0.1"
#:package InfisicalDotNet@1.0.1
#addin nuget:?package=InfisicalDotNet&version=1.0.1
#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.
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 | Versions 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. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net8.0
- BouncyCastle.Cryptography (>= 2.2.1)
- Microsoft.Extensions.Configuration (>= 8.0.0)
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 | 189 | 2/4/2024 |
| 1.0.1 | 524 | 2/4/2024 |
| 1.0.1-alpha.26 | 118 | 2/4/2024 |
| 1.0.1-alpha.25 | 807 | 11/4/2023 |
| 1.0.1-alpha.23 | 166 | 11/4/2023 |
| 1.0.1-alpha.22 | 124 | 11/4/2023 |
| 1.0.1-alpha.20 | 157 | 11/3/2023 |
| 1.0.1-alpha.18 | 160 | 11/2/2023 |
| 1.0.1-alpha.15 | 147 | 11/2/2023 |
| 1.0.1-alpha.14 | 122 | 11/2/2023 |
| 1.0.1-alpha.12 | 128 | 11/2/2023 |
| 1.0.0-alpha.9 | 143 | 11/2/2023 |