Stratara.Infrastructure
3.1.6
dotnet add package Stratara.Infrastructure --version 3.1.6
NuGet\Install-Package Stratara.Infrastructure -Version 3.1.6
<PackageReference Include="Stratara.Infrastructure" Version="3.1.6" />
<PackageVersion Include="Stratara.Infrastructure" Version="3.1.6" />
<PackageReference Include="Stratara.Infrastructure" />
paket add Stratara.Infrastructure --version 3.1.6
#r "nuget: Stratara.Infrastructure, 3.1.6"
#:package Stratara.Infrastructure@3.1.6
#addin nuget:?package=Stratara.Infrastructure&version=3.1.6
#tool nuget:?package=Stratara.Infrastructure&version=3.1.6
Stratara.Infrastructure
License: MIT.
Cross-cutting infrastructure plumbing for the Stratara framework — the Tier-C glue that lets downstream apps wire authorization, DI composition, and worker-stack configuration with a single reference.
Contents
- Authorization decorators over command-outbox dispatch (
AuthorizingCommandOutboxDispatcher). - DI composition helpers that wire Mediator, Outbox, Identity, and EFCore into a hosted app.
- Configuration providers and option binders used by the worker stack.
Dependencies
Transitively depends on Stratara.Contracts, Stratara.EventSourcing.EntityFrameworkCore, Stratara.Mediator, Stratara.Outbox.RabbitMQ, Stratara.Sessions, Stratara.Shared.
Behavioural notes
AddSecurity() — IKeyStore registration (since 3.0.11)
AddSecurity() registers Stratara's security stack including the IKeyStore abstraction. The default is a TryAddSingleton<IKeyStore, DummyKeyStore> fallback — but DummyKeyStore since 3.0.11 throws InvalidOperationException in any environment other than Development (whitelist guard to prevent production data exposure from the demo encryption key). Hosts on Staging, QA, UAT, Preview, or any custom environment must register a real IKeyStore implementation before calling AddSecurity():
// Recommended composition root
if (builder.Environment.IsDevelopment())
{
builder.Services.AddSecurity(); // DummyKeyStore fallback is fine
}
else
{
builder.Services.AddSingleton<IKeyStore, AzureKeyVaultKeyStore>(); // or AwsKmsKeyStore, HsmKeyStore, ...
builder.Services.AddSecurity();
}
KeyStoreStartupProbe logs a Warning (event id LogEvents.KeyManagement.DummyKeyStoreActive = 112_001) at host start when the resolved IKeyStore is DummyKeyStore — even in Development — so an accidental dependency on the dummy is loud rather than silent.
Why the change: Before 3.0.11 the guard only blocked IsProduction(). Hosts in any other environment silently encrypted with the world-known constant pass-phrase "StrataraTestKey" baked into the shipping NuGet — a Staging or QA copy of production data could be decrypted by anyone reading the source. The whitelist guard makes this configuration crash-fast at host build instead of allowing silent data exposure.
AddCaching() — Redis registration
AddCaching() used to delegate to builder.AddRedisClient("redis") from Aspire.StackExchange.Redis. After the Aspire-wrapper removal it registers IConnectionMultiplexer directly via ConnectionMultiplexer.Connect(...) from StackExchange.Redis. The method signature is unchanged, but the Aspire-only side-effects are gone:
- No automatic Redis health check. Add one explicitly with
AddHealthChecks().AddRedis(connectionString)(fromAspNetCore.HealthChecks.Redis) if your host exposes/healthand you want Redis covered. - No automatic OpenTelemetry Redis instrumentation. Add
OpenTelemetry.Instrumentation.StackExchangeRedisand.AddRedisInstrumentation()to yourTracerProviderBuilderif you want Redis spans in your traces.
The connection-string lookup (ConnectionStrings:redis in configuration) is identical to the pre-cleanup behaviour.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. 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. |
-
net10.0
- Azure.Identity (>= 1.21.0)
- Microsoft.AspNetCore.Http.Abstractions (>= 2.3.10)
- Microsoft.Extensions.Configuration.Abstractions (>= 10.0.8)
- Microsoft.Extensions.DependencyInjection (>= 10.0.8)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.8)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.8)
- StackExchange.Redis (>= 2.13.10)
- Stratara.Contracts (>= 3.1.6)
- Stratara.EventSourcing.EntityFrameworkCore (>= 3.1.6)
- Stratara.Mediator (>= 3.1.6)
- Stratara.Outbox.RabbitMQ (>= 3.1.6)
- Stratara.Security (>= 3.1.6)
- Stratara.Sessions (>= 3.1.6)
- Stratara.Shared (>= 3.1.6)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on Stratara.Infrastructure:
| Package | Downloads |
|---|---|
|
Stratara.EventSourcing.WorkerDefaults
Worker-host wiring composites for the Stratara event-sourced stack. IHostApplicationBuilder extensions (AddBackendServices, AddCommandWorkerServices, AddEventProjectionWorkerServices, AddSagaWorkerServices, AddOutboxWorkerServices) bundle the per-concern DI calls so each worker host opts in with one line. |
|
|
Stratara.Testing.EntityFrameworkCore
Spin up the real Stratara event-sourcing write stack (EventSource, aggregation, snapshots, the EF Core write store) against a shared in-memory SQLite database in one call — production code paths, no Postgres, no Docker. Builds on Stratara.Testing's in-memory doubles. |
GitHub repositories
This package is not used by any popular GitHub repositories.
### Changed
- **License changed from FSL-1.1-MIT to the MIT License.** Stratara is now OSI-approved open
source — free for any use, including commercial, with no competition clause and no two-year
conversion delay. The previous Functional Source License (source-available, converting to MIT
two years after each release) has been replaced outright. Package metadata now declares the
SPDX expression `MIT` (`PackageLicenseExpression`), so nuget.org renders a standard clickable
MIT license label instead of an embedded custom-license file. The `LICENSE` file at the repo
root now contains the standard MIT text and is still bundled into every package. No code or API
changes accompany this — it is purely a licensing and metadata change. Previously published
versions (3.0.20 through 3.1.5) remain under the FSL terms they shipped with; this change applies
to all versions released from here on.