Delete the modules/operation-rate-limiting projects and their EF Core/application tests, remove InvalidateCacheAsync from the dynamic policy store, and update the error code namespace, localization keys and documentation to the framework-only layout.
Add LINGYUN.Abp.OperationRateLimiting.Abstractions for models, attributes, enums and constants, keep the interfaces in the core package, remove the Redis state accessor in favor of rule reset/release services, align the management rule records, and split the tests into core, EF Core, application and Redis projects.
Use conventional DI for the static policy store, null dynamic store, Redis executor and Redis state accessor instead of explicit service registrations; rename the options-backed static store to StaticOperationRateLimitingPolicyStore.
Remove IOperationRateLimitingStore and the algorithm switch. Rules now own the algorithm logic and use IOperationRateLimitingStateAccessor for state, with Redis Lua rule implementations and a CAS state accessor.
- Regenerate the CLI api description from the blob-management module so it matches
the module snapshot and no longer exposes TenantId
- The previous snapshot was host-wide and carried 520 unrelated types (Elsa,
System.Reflection, Asp.Versioning); the controller/action surface is unchanged (31)
- Remove the stale TenantId parameter and property of BlobDownloadByNameInput from
the CLI api-description snapshot so it matches the updated contract DTO
- Regenerate the CLI api description from the blob-management module so it matches
the module snapshot and no longer exposes TenantId
- The previous snapshot was host-wide and carried 520 unrelated types (Elsa,
System.Reflection, Asp.Versioning); the controller/action surface is unchanged (31)
- Remove the stale TenantId parameter and property of BlobDownloadByNameInput from
the CLI api-description snapshot so it matches the updated contract DTO
- Remove the client-controlled TenantId from BlobDownloadByNameInput and drop the
download/by-name/t/{tenantId}/{name} route
- Do not switch the tenant from request data in BlobAppService; the policy check now
enforces the functional permission and the container/resource policy together
- Route id-based download, delete and download-url generation through the container
policy so resource grants of the users container cannot be bypassed
- Add a blob tenant ownership check and resolve storage of by-key downloads in the
tenant carried by the key
Every channel needs its own message shape (a WeChat Work template card, a webhook news
article, a wx-pusher URL), but the only way to carry it was to stuff those types into
`NotificationData`, which couples the producer to the channels and forces a schema change
whenever a channel gains a field. Channels now declare their own payload types and the
property bag carries them under per channel key prefixes, so one `ExtraProperties` column
serves every channel and no notification table has to change.
- add the channel data contract to `LINGYUN.Abp.Notifications.Core`:
`NotificationChannelData` base type, `[NotificationChannelData]` /
`[NotificationChannelProperty]` annotations, `NotificationChannelDataDescriptor`,
`NotificationChannelDataFormat` and `NotificationChannelDataPresenceMode`
- add the implementation to `LINGYUN.Abp.Notifications`: `INotificationChannelDataResolver`
dispatching payloads in priority order, `INotificationChannelDataAccessor` reading and
writing typed values in the property bag, `INotificationChannelDataSerializer` for the
producer side, `INotificationChannelDataPresenceProvider`, `AbpNotificationChannelDataOptions`
and `AbpNotificationChannelDataConfigurationException` for registration time validation
- keys are namespaced per channel (`wx-work:`, `wx-work-hook:`, `wx-mp:`, `pusher:`, `plus:`)
and matched case insensitively, so channels cannot collide in the shared property bag;
complex payloads are stored as JSON strings and deserialized back with the configured
`IJsonSerializer`
- the WeChat Work channel gains 18 channel data types plus `WeChatWorkMessageFactory`, and
the webhook channel 16 plus `WeChatWorkWebhookMessageFactory`, covering text, markdown,
markdown_v2, image, news, file, voice, template card, mini program notice and mp news
- PushPlus, WxPusher and the WeChat mini program channel adopt the same contract; the mini
program keys are prefixed and the historical bare keys are kept as a read only fallback,
marked `[Obsolete]` with the provider's `ApplyLegacyKeys` as the only sanctioned read site
- delete the WxPusher `NotificationDataExtensions.SetUrl` in favour of the typed accessor
- add `WebhookTemplateCardSystemTextJsonConverter` so the abstract webhook template card
survives the property bag round trip, and make `WeChatWorkWebhookNewsMessage` public
- test projects `LINGYUN.Abp.Notifications.ChannelData.Tests`, `...PushPlus.Tests`,
`...WeChat.Work.Tests` and `...Webhook.WeChat.Work.Tests` (real ABP container, fake
senders registered through `context.Services.Replace` so no real API is called), the
mini program and wx-pusher tests now drive a fake sender, and each channel verifies
payloads restored from a raw database JSON string as well as from memory
The template card payload is written into the notification property bag as JSON and read
back when the notification is published, but TemplateCard is abstract, so Newtonsoft.Json
could never restore it ("Could not create an instance of type ... abstract class") and the
card was lost as soon as the notification was persisted or queued for a retry.
- add TemplateCardJsonConverter and TemplateCardSystemTextJsonConverter, which resolve the
concrete card from the card_type discriminator (read from the constructor IL, falling back
to the type name) and reject an unknown discriminator
- split NotificationDataWeChatWorkExtensions into partials per message type (file, mini
program, mp news, template card, text card, video, voice) and add the shared
TryGetMessagePayload helper that deserializes with the converter
- add the Safe, EnableIdTrans, EnableDuplicateCheck and DuplicateCheckInterval switches
- migrate TuiJuheNotificationPublishProvider to the NotificationPublishContext contract the
other providers already use, and skip the interceptors for notifications at or above Warn
- bind the WeChat Work mini program account through the new work-weixin/miniprogram/bind
endpoint using the code2session user id
- rename AbpNotificationOptions to AbpNotificationsPublishOptions in the tests, fix the SMS
test project reference, retarget the templating tests to net10.0, register the webhook
notification projects and add the missing IP2Region reference
Give the OAuth login and the mini program login their own WeChat Work grant types instead
of sharing one, and add the code2session exchange the mini program flow needs.
- AbpWeChatWorkGlobalConsts.GrantType becomes OAuthGrantType with the value "wecom_oauth",
and MiniProgramGrantType ("wecom_mp") is added
- WeChatWorkTokenExtensionGrant becomes abstract and exposes a FindUserInfoAsync hook;
WeChatWorkOAuthTokenExtensionGrant keeps the existing user info exchange and the new
WeChatWorkMiniProgramTokenExtensionGrant exchanges the js code through
IWeChatWorkUserFinder.GetCode2SessionAsync
- add the code2session model, response and mapping, plus the
/cgi-bin/miniprogram/jscode2session client call
- register both grant types in AbpOpenIddictWeChatWorkModule and allow both custom flows
in AllowWeChatWorkFlow, and migrate the remaining GrantType call sites
BREAKING CHANGE: AbpWeChatWorkGlobalConsts.GrantType was removed and its value changed, so
clients that authenticate with grant_type "wecom" must switch to "wecom_oauth"; the public
WeChatWorkTokenExtensionGrant is now abstract and must be subclassed.
configureawait.props now provides the ConfigureAwait weaver through the Fody 6.9.3
WeaverConfiguration property and sets FodyGenerateXsd=false, so the per-project
FodyWeavers.xml files and every FodyWeavers.xsd are redundant.
- delete 450 FodyWeavers.xml and 438 FodyWeavers.xsd from the framework, modules,
services, gateways, tests and migrations projects and from the micro service template
- every removed FodyWeavers.xml was equivalent to the default supplied by configureawait.props
(439 x <ConfigureAwait ContinueOnCapturedContext="false" />, 20 x <ConfigureAwait />, whose
default is ContinueOnCapturedContext=false, and 2 of those with an XML declaration); no
Blazor / AspNetCore.Components project carried one and the template manifests do not list them
- the aio template keeps its 22 files: its own Directory.Packages.props pins Fody 6.8.0, which
does not support the WeaverConfiguration property
GeoLite2 is licensed by MaxMind and must not be redistributed, so the module no longer
ships or embeds the database: the consumer supplies it at deployment time, and a missing
file degrades to empty results instead of failing the host.
...
BREAKING CHANGE: AbpMaxMindGeoIP2Module.DefaultDatabaseFile was removed and the module no
longer embeds GeoLite2-City.mmdb. Hosts must download a GeoLite2 database and configure
MaxMindGeoIP2:DatabaseFile; without it IP location resolution returns empty results.
Migrate the local file system blobs written by the legacy OssManagement to
BlobManagement, so an existing deployment can be moved to the new storage
without touching the files by hand.
- add BlobMigrationCommand (blob-migration): walk the working directory and upload
every file matching the search pattern through IBlobIntegrationService; the options
cover the working directory (-wd), the search option (-so) and pattern (-sp), the
bucket (-bn), the blob path (-pn) and name (-on), the service url (-u), the tenant
(-t) and overwrite (-ow), plus a list only mode (-ls) to confirm the blob names first
- add ICurrentBlob/CurrentBlob and BlobHttpClientHandler so the command can retarget the
client proxies to the given BlobManagement url, send the __tenant header and skip the
result wrapper for the current run
- register the BlobManagement static client proxies and AbpHttpClientModule in
AbpCliModule, and embed the generated ClientProxies json into the assembly
- add the Volo.Abp.Ddd.Application.Contracts and Volo.Abp.Http.Client references, and make
CreateCommand.GetUsageInfo virtual so the new command can reuse it
- set an output template for the file logger and split the launchSettings profiles into
one profile per command
Serilog enrichers:
- AbpLoggingSerilogElasticsearchModule and AbpLoggingSerilogOpenObserveModule now depend on
AbpSerilogEnrichersApplicationModule and AbpSerilogEnrichersUniqueIdModule, so the providers
pull in the ApplicationName / UniqueId enrichers their queries rely on
- add the corresponding project references (and drop the unused LINGYUN.Linq.Dynamic.Queryable
reference from the Elasticsearch logging package, add Serilog.Sinks.OpenTelemetry to the
OpenObserve logging package)
Documentation:
- add aspnet-core/framework/logging/README.md: a directory level index covering all five logging
modules (core Logging, the Elasticsearch and OpenObserve ILoggingProvider implementations and
the two Serilog enrichers) with module references, configuration options and notes
- document the OpenObserve audit log store in aspnet-core/framework/auditing/README.md:
storage support, module reference, AuditLogging:OpenObserve options and the platform notes
(per-tenant streams, append-only/delete not supported, flattened nested arrays, stream creation)
- add the missing English README of LINGYUN.Abp.Logging.Serilog.OpenObserve (the Chinese one linked
to a file that did not exist) and document that the condition parser / SQL builder helpers moved
from LINGYUN.Abp.Logging.Serilog.OpenObserve.Utils to LINGYUN.Abp.OpenObserve.Utils
Add an OpenObserve implementation of the audit logging stores as an alternative to
Elasticsearch: audit logs, security logs, entity changes and actions go into separate
streams and are queried with OpenObserve SQL.
LINGYUN.Abp.AuditLogging.OpenObserve:
- AbpAuditLoggingOpenObserveOptions binds AuditLogging:OpenObserve; the child streams are
derived from AuditLogStream (GetEntityChangeStream/GetActionStream), no separate options
- OpenObserveAuditLogWriter / OpenObserveSecurityLogWriter replace IAuditLogWriter /
ISecurityLogWriter; OpenObserveAuditLogManager / OpenObserveSecurityLogManager replace
IAuditLogManager / ISecurityLogManager; OpenObserveEntityChangeStore replaces IEntityChangeStore
- entity changes and actions are flattened into their own streams; Actions.* conditions use a
two-step query (match auditlogid in the actions stream, then filter the main stream by id),
because OpenObserve cannot query nested arrays structurally
- multi-tenancy: stream names are per tenant (audit_log_{tenantId:N}) via
IOpenObserveStreamNameNormalizer; writes resolve the log's own tenant, queries the current one
- writes may override _timestamp with the log time (AuditLog.ExecutionTime /
SecurityLog.CreationTime), bounded by TimestampAllowedUptoHours since OpenObserve only accepts
data within ZO_INGEST_ALLOWED_UPTO (5 hours by default)
- entity change details and _timestamp are handled by OpenObserveEntityChangeConverter through
IAuditLoggingOpenObserveSerializer (ABP IJsonSerializer by default), so entities never use
JsonSerializer directly
- deletion is not supported by OpenObserve (append-only, no DELETE/UPDATE): DeleteAsync /
DeleteManyAsync throw the business exception AuditLoggingOpenObserve:010001
("当前日志设施不支持删除记录!" / "The current logging facility does not support deleting records!")
backed by a zh-Hans/en localization resource
- a stream that does not exist yet (nothing ingested) yields an empty result and logs a warning
instead of failing
Shared infrastructure:
- move Condition / ComparisonOp / ExpressionParser from LINGYUN.Abp.Logging.Serilog.OpenObserve
to LINGYUN.Abp.OpenObserve (the parser now also handles Any(member) expressions) and add
OpenObserveSqlBuilder for SQL condition building
Tests:
- LINGYUN.Abp.AuditLogging.OpenObserve.Tests runs the shared AuditLogManager_Tests suite (delete
hooks overridden to assert the not-supported exception) plus tests for the timestamp helper,
localization, entity change round-trip, multi-tenant isolation and the missing-stream warning;
test streams are unique per host instance and cleaned up on shutdown
- AuditLogManager_Tests gains virtual DeleteAsync / DeleteManyAsync hooks (default behaviour unchanged)
Introduce an extension point that lets modules enrich audit/security log entries
before they are queued or written, instead of having to replace the whole store.
- add IAuditLogInfoContributor / ISecurityLogInfoContributor together with
AuditLogInfoContributorContext / SecurityLogInfoContributorContext
(IServiceProviderAccessor + the log info being enriched)
- AbpAuditLoggingOptions gains AuditLogInfoContributors / SecurityLogInfoContributors;
AuditingStore and SecurityLogStore run them (guarded by Any()) inside a fresh
service scope before enqueueing or writing the log
- LINGYUN.Abp.AuditLogging.IP.Location now contributes the resolved IP location
through that extension point instead of replacing IAuditingStore / ISecurityLogStore:
remove IPLocationAuditingStore and IPLocationSecurityLogStore, add
IPLocationAuditLogInfoContributor / IPLocationSecurityLogInfoContributor and
IPLocationConstants, and have AbpAuditLoggingIPLocationModule register both contributors
- document AbpAuditLoggingIPLocationOptions (section AuditLogging:IPLocation,
environment variable AuditLogging__IPLocation__IsEnabled) and make its default
IsEnabled = false explicit
- EfCoreAuditLogManager.GetAsync uses FindAsync with a nullable mapping so that a
missing audit log returns null instead of throwing
Note: the IP location remark is now stored under the "IPLocation" extra property
(previously "Location").
- AbpIPLocationResolveOptions: replace the UseCountry/UseProvince predicates with the
RemoveCountry/RemoveProvince name arrays and bind them from the new "IPLocation"
configuration section in AbpIPLocationModule
- IPLocationResolveContributorBase: shared remark rules for every provider
(province matches RemoveProvince -> city only; country matches RemoveCountry ->
province + city with the same-name collapse; otherwise country only; empty remarks
when every part was removed)
- document the rules, the IPLocation section and the environment variables in the
LINGYUN.Abp.IP2Region and LINGYUN.Abp.MaxMindGeoIP2 READMEs
Rename the single (monolith) application, its migration projects and the
associated solution file to follow the LINGYUN.Abp.MicroService.* naming
convention.
Renamed projects:
- LY.MicroService.Applications.Single
-> LINGYUN.Abp.MicroService.AllInOne
- LY.MicroService.Applications.Single.EntityFrameworkCore
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore
- LY.MicroService.Applications.Single.EntityFrameworkCore.MySql
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.MySql
- LY.MicroService.Applications.Single.EntityFrameworkCore.PostgreSql
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.PostgreSql
- LY.MicroService.Applications.Single.EntityFrameworkCore.SqlServer
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.SqlServer
- LY.MicroService.Applications.Single.DbMigrator
-> LINGYUN.Abp.MicroService.AllInOne.DbMigrator
- aspnet-core/LINGYUN.MicroService.SingleProject.slnx
-> aspnet-core/LINGYUN.MicroService.AllInOne.slnx
Renamed identifiers:
- MicroServiceApplicationsSingleModule -> AllInOneModule
(AllInOneModule.cs, AllInOneModule.Configure.cs, referenced from Program.cs)
Also updated:
- namespaces, <RootNamespace>, ProjectReference paths and the solution entries
- Dockerfile entry point (LINGYUN.Abp.MicroService.AllInOne.dll)
- build/build-aspnetcore-common.ps1 (solution array)
- README.md / README.en.md (solution list) and the project READMEs / docs that
referenced the previous names
Code fixes required by the new namespace (namespaces under LINGYUN.Abp shadow
top-level namespaces):
- SingleMigrationsDbContext: fully qualify LINGYUN.Platform.Datas.Data, because
the simple name Data now resolves to the LINGYUN.Abp.Data.* namespace
- AllInOneModule.Configure: use global::Elsa.* for the Elsa startup types,
because Elsa.Activities.* now resolves to LINGYUN.Abp.Elsa.Activities.*
(Elsa.Activities.Webhooks.Startup would otherwise silently bind to the wrong type)
BREAKING CHANGE: assembly names, namespaces, the Docker entry point and the
published package ids of the migration projects changed. Consumers must update
their references:
- LY.MicroService.Applications.Single.EntityFrameworkCore
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore
- LY.MicroService.Applications.Single.EntityFrameworkCore.MySql
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.MySql
- LY.MicroService.Applications.Single.EntityFrameworkCore.PostgreSql
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.PostgreSql
- LY.MicroService.Applications.Single.EntityFrameworkCore.SqlServer
-> LINGYUN.Abp.MicroService.AllInOne.EntityFrameworkCore.SqlServer
- LY.MicroService.Applications.Single.DbMigrator
-> LINGYUN.Abp.MicroService.AllInOne.DbMigrator
Stale package artifacts in the LocalNuget output folders were removed; rebuild
(or pack) to regenerate them with the new names.
Verified:
- dotnet build aspnet-core/LINGYUN.MicroService.AllInOne.slnx (0 errors)
- all six renamed projects build with 0 errors
- 196 tracked files were relocated (193 detected as renames), no tracked file lost
- text scan for the previous names returns no remaining references
Note: aspnet-core/templates/aio still declares MicroServiceApplicationsSingleModule;
renaming the AIO template is intentionally left for a follow-up.
- Retrieve the last sorting index by reversing the sorting order.
- Obtain the index mapping using pattern matching
- Add the extension for obtaining ES error messages