backend scaffold
This commit is contained in:
@@ -0,0 +1,35 @@
|
||||
# Dev 的配置,由 scripts/deploy-dev.sh apply 到内网 k3s 集群的 retailapp-dev namespace。
|
||||
# Dev 的数据库跑在同一台 Ubuntu 机器上(不是 Azure Flexible Server),所以连的是集群内的 Service。
|
||||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: conti-backend-env
|
||||
namespace: retailapp-dev
|
||||
data:
|
||||
DB_HOST: "mysql.retailapp-dev.svc.cluster.local"
|
||||
DB_USERNAME: "conti"
|
||||
SECURITY_JWT_ACTIVE_KEY_ID: "v1"
|
||||
# Dev 环境暂时没有可用的 F6 / O2O 联调地址,先指向不存在的地址,
|
||||
# 走的就是降级路径——这本身也是对 fallback 的一次真实验证(见 05-integration-layer.md)
|
||||
F6_BASE_URL: "http://f6-not-available.retailapp-dev.svc.cluster.local"
|
||||
MINI_BASE_URL: "http://mini-not-available.retailapp-dev.svc.cluster.local"
|
||||
---
|
||||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: conti-backend-config
|
||||
namespace: retailapp-dev
|
||||
data:
|
||||
application-dev.yml: |
|
||||
# Dev 上放开到 DEBUG,方便团队排查;改这一项是热更新的典型用例,
|
||||
# 改完 15 秒生效,不用重新部署
|
||||
logging:
|
||||
level:
|
||||
com.continental.retailapp: DEBUG
|
||||
|
||||
resilience4j:
|
||||
circuitbreaker:
|
||||
instances:
|
||||
f6-api:
|
||||
failure-rate-threshold: 50
|
||||
slow-call-duration-threshold: 1500ms
|
||||
Reference in New Issue
Block a user