fix: 更新 DefaultIpHeaderName 以包含 Cf-Connecting-Ip 標頭 #296
arenchenci-cd.yml
on: push
Build Netcorext.Auth.API
1m 21s
Build Netcorext.Auth.Authentication
1m 22s
Build Netcorext.Auth.Authorization
1m 13s
Build Netcorext.Auth.Gateway
1m 13s
Deploy Netcorext.Auth.Abstractions
0s
Deploy Netcorext.Auth.Extensions.AspNetCore
0s
Deploy Netcorext.Auth.Protobufs
0s
Annotations
7 warnings
|
Build Netcorext.Auth.Authorization
Skip output 'image' since it may contain secret.
|
|
Build Netcorext.Auth.Gateway
Skip output 'image' since it may contain secret.
|
|
Build Netcorext.Auth.API
Skip output 'image' since it may contain secret.
|
|
Build Netcorext.Auth.API
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build Netcorext.Auth.API:
src/Netcorext.Auth.API/Services/Permission/Queries/GetFunctionId/GetFunctionIdHandler.cs#L16
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build Netcorext.Auth.API:
src/Netcorext.Auth.API/Services/Permission/Queries/GetFunctionId/GetFunctionIdHandler.cs#L16
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
Build Netcorext.Auth.Authentication
Skip output 'image' since it may contain secret.
|