Logging:
- reference LINGYUN.Abp.Logging.Serilog.OpenObserve and register
AbpLoggingSerilogOpenObserveModule (the Elasticsearch module is now declared
explicitly in the module dependencies)
- wrap the Serilog WriteTo pipeline in an Async sink and add an OpenTelemetry
sink (endpoint, protocol, resource attributes)
- set Logging:Provider to ElasticsearchLoggingProvider and add the OpenObserve
endpoint/token to the development settings
- add the Serilog.Sinks.Async / Serilog.Sinks.Console / Serilog.Sinks.OpenTelemetry
package references
- rotate the file sinks by size as well (rollOnFileSizeLimit, retainedFileCountLimit
50, fileSizeLimitBytes 5 MB)
Solutions:
- add LINGYUN.Abp.Logging.Serilog.OpenObserve to the AllInOne solution and remove
the duplicated /tests/ folder (those test projects stay in LINGYUN.MicroService.All.slnx)
- add LINGYUN.Abp.MaxMindGeoIP2 to the Aspire solution
Auth:
- accept the API resource audience of this host: AuthServer:ValidAudiences now also
contains "all_in_one" (the access token audience comes from the API scope resource
created in OpenIddictDataSeederContributor), so OpenIddict validation no longer
rejects tokens with ID2094
- the JwtBearer scheme now applies ValidAudiences from configuration as well, together
with the wildcard issuer validator configuration
Also: global usings tidied up (LINGYUN.Abp.IP.Location is no longer needed by the host).
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.
- Add the interface for generating download links
- Alibaba Cloud Object Storage adds configuration for the expiration time of pre-signed links
- Tencent Cloud Object Storage adds configuration for the expiration time of pre-signed links
- Add generation of download url feature
- Add the setting item for the expiration time of the generated download url
- Add the interface for parsing file ContentType
- Integrate the MimeCheck module to parse the Content-Type of the file
- Upgrade elsa 2.x to 2.15.2
- Redirecting the `Rebus.RabbitMq` package version resolves the compatibility issue of the` RabbitMQ.Client` 6.x
- Add `LINGYUN.Abp.Elsa.Designer`
- Swagger has added the oauth config
- The cors configuration can be a string array
- Add cross-domain initialization configuration for the microservice oauth client