BccCode.Privacy.Wolverine
0.5.1
See the version list below for details.
dotnet add package BccCode.Privacy.Wolverine --version 0.5.1
NuGet\Install-Package BccCode.Privacy.Wolverine -Version 0.5.1
<PackageReference Include="BccCode.Privacy.Wolverine" Version="0.5.1" />
<PackageVersion Include="BccCode.Privacy.Wolverine" Version="0.5.1" />
<PackageReference Include="BccCode.Privacy.Wolverine" />
paket add BccCode.Privacy.Wolverine --version 0.5.1
#r "nuget: BccCode.Privacy.Wolverine, 0.5.1"
#:package BccCode.Privacy.Wolverine@0.5.1
#addin nuget:?package=BccCode.Privacy.Wolverine&version=0.5.1
#tool nuget:?package=BccCode.Privacy.Wolverine&version=0.5.1
BccCode.Privacy.Wolverine
BCC Privacy for Wolverine. Part of the BCC Privacy package family; depends
on BccCode.Privacy and Wolverine only.
builder.Host.UseWolverine(opts =>
{
opts.UsePrivacy(); // the scope on envelopes, and before every handler
opts.PublishPrivacyMoments(); // starts and ends of bases at their moment; BasisChanged published
});
builder.Services.AddPrivacyMoments<AppDbContext>(); // from BccCode.Privacy.EntityFrameworkCore
[PrivacyProcess(Processes.EventRegistration)] // optional: the handler's own process
public static class RegistrationHandler { public static Task Handle(Register m, AppDbContext db) => /* ... */; }
| Behaviour | |
|---|---|
| A message sent while handling a request or another message | Carries the sender's organisation and process (bcc-privacy-org, bcc-privacy-process headers) |
| A handler | Runs under the organisation on the envelope and the process it declares (on the handler method, class or message type), else the one on the envelope |
| A handler without a process that reads personal data | Refused, naming the message type and the fix |
| A message without an organisation | The handler sees no personal rows |
| A basis's start or end | Applied at its moment (a pass starts at the next pending moment, and at least every 10 s); a rolled-back save leaves no moment |
BasisChanged |
Published through Wolverine at least once, with the outbox id as Id; receivers drop repeats by it. After a crash, what was stored but not published goes out on restart |
An installer that has the service collection rather than the Wolverine options (such as
BccCode.Privacy.Hosting's AddPrivacy()) calls services.AddPrivacyWolverine() instead: since
Wolverine 3, an extension added with ConfigureWolverine may not register services.
Route BasisChanged to where it should go (a local handler or a subscriber); Wolverine drops a
message with no route. Use a durable outbox and inbox for delivery across restarts.
Version 0.x. Licence: Apache 2.0. Source: bcc-code/bcc-privacy, libraries/dotnet.
| 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
- BccCode.Privacy (>= 0.5.1)
- Microsoft.Extensions.Caching.Memory (>= 10.0.15)
- Microsoft.Extensions.Compliance.Abstractions (>= 10.11.0)
- WolverineFx (>= 6.64.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on BccCode.Privacy.Wolverine:
| Package | Downloads |
|---|---|
|
BccCode.Privacy.Hosting
One AddPrivacy() for BCC Privacy: the EF Core, ASP.NET Core and Wolverine packages wired together, defaults per environment, the privacy document at /.well-known/bcc-privacy, and the application's processes and data items pushed to the Privacy API at deploy. |
GitHub repositories
This package is not used by any popular GitHub repositories.