timerzz
ee9fab7a8f
All checks were successful
Build image / build (push) Successful in 1m15s
- 在Provider服务中添加Redis订阅客户端，用于配置变更通知 - 在UpdateProvider方法中添加配置变更发布逻辑 - 优化Provider初始化方法，支持传入Redis客户端 - 修复Provider状态字典的常量引用问题 - 完善Provider相关API的日志记录"
25 lines
1.1 KiB
YAML
25 lines
1.1 KiB
YAML
apiVersion: v2
|
|
name: provider
|
|
description: 可达鸭海淘，供应商管理后端。
|
|
|
|
# A chart can be either an 'application' or a 'library' chart.
|
|
#
|
|
# Application charts are a collection of templates that can be packaged into versioned archives
|
|
# to be deployed.
|
|
#
|
|
# Library charts provide useful utilities or functions for the chart developer. They're included as
|
|
# a dependency of application charts to inject those utilities and functions into the rendering
|
|
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
|
|
type: application
|
|
|
|
# This is the chart version. This version number should be incremented each time you make changes
|
|
# to the chart and its templates, including the app version.
|
|
# Versions are expected to follow Semantic Versioning (https://semver.org/)
|
|
version: 1.0.1
|
|
|
|
# This is the version number of the application being deployed. This version number should be
|
|
# incremented each time you make changes to the application. Versions are not expected to
|
|
# follow Semantic Versioning. They should reflect the version the application is using.
|
|
# It is recommended to use it with quotes.
|
|
appVersion: "v1.0.1"
|