blp/railwaysystem
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(qa): isolate legacy database clients with owned transport guard

Browse Source
This commit is contained in:
wangzhibiao committed 2026-10-15 02:54:00 +08:00
1 parent 65c567152e
commit 01e949093a
9 files changed
+577 -23
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

qa-bootstrap/round5v.env.example
+3 -1
View File
@@ -1,6 +1,8 @@
# COPY outside Git, chmod 600. Literal KEY=value only, no shell expansion.
# Never reuse the old QA_DB_URL from another database.
FUSION_QA_DB_URL='jdbc:kingbase8://192.168.139.218:4321/railwaysystem_fusion_qa_20261013?connectTimeout=5&socketTimeout=15'
# For start: qa.py takes the URL from a live qa_isolation.py lease when this key is absent.
# Do not use the legacy 14321 endpoint or a raw direct connection for application start.
# If explicitly supplied, FUSION_QA_DB_URL must match the owned loopback port/database exactly.
FUSION_QA_APP_PASSWORD='REPLACE_WITH_APPROVED_APP_PASSWORD'
TRAIN_STUDENT_IDENTITY_ENCRYPTION_KEY='REPLACE_WITH_APPROVED_QA_ENCRYPTION_KEY'
TRAIN_STUDENT_IDENTITY_HASH_KEY='REPLACE_WITH_APPROVED_QA_HASH_KEY'