You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`LONGPORT_SECRET_NAME`| No | Secret Manager secret name for LongPort token (default: `longport_token`) |
84
84
|`ACCOUNT_PREFIX`| No | Alert/log prefix for account/environment (default: `DEFAULT`) |
85
85
|`SERVICE_NAME`| No | Alert/log prefix for service identity (default: `longbridge-quant`) |
86
+
|`STRATEGY_PROFILE`| No | Strategy profile selector (default: `semiconductor_rotation_income`, currently the only supported value) |
87
+
|`ACCOUNT_REGION`| No | Account region marker for platform-style deployment (e.g. `HK`, `SG`; defaults to `ACCOUNT_PREFIX` / service-name suffix / `DEFAULT`) |
86
88
|`NOTIFY_LANG`| No | Notification language: `en` (English, default) or `zh` (Chinese) |
87
89
|`GOOGLE_CLOUD_PROJECT`| No | GCP project ID (defaults to ADC project when unset) |
88
90
@@ -95,6 +97,8 @@ Deploy the same codebase as multiple Cloud Run services (e.g. `HK` and `SG`) by
95
97
-`LONGPORT_SECRET_NAME`: point to different secrets (e.g. `longport_token_hk`, `longport_token_sg`)
96
98
-`ACCOUNT_PREFIX`: e.g. `HK`, `SG` (all Telegram/log alerts will include `[ACCOUNT_PREFIX/SERVICE_NAME]`)
97
99
-`SERVICE_NAME`: e.g. `longbridge-quant-hk`, `longbridge-quant-sg`
100
+
-`STRATEGY_PROFILE`: use `semiconductor_rotation_income` for the current LongBridge strategy profile
101
+
-`ACCOUNT_REGION`: explicitly mark the deployed account region (`HK` / `SG`); if unset, the app falls back to `ACCOUNT_PREFIX` or the `-hk` / `-sg` service-name suffix
On every push to `main`, the workflow updates both Cloud Run services with the shared and per-environment values above, and removes `TELEGRAM_CHAT_ID` from each Cloud Run service.
@@ -131,7 +136,7 @@ Important:
131
136
132
137
-`QuantPlatformKit` is only a shared dependency; Cloud Run still deploys `LongBridgeQuant` itself.
133
138
- Recommended Cloud Run service names: `longbridge-quant-hk` and `longbridge-quant-sg`.
134
-
- Keep using two triggers and two GitHub Environments. The split key is still `CLOUD_RUN_SERVICE + CLOUD_RUN_REGION`.
139
+
- Keep using two triggers and two GitHub Environments. The split key is still `CLOUD_RUN_SERVICE + CLOUD_RUN_REGION`, and the runtime identity is now explicit through `STRATEGY_PROFILE + ACCOUNT_REGION`.
135
140
- If you later rename or move this repository, rebuild the GitHub source binding in Google Cloud for both triggers instead of assuming the existing source binding will follow the rename.
136
141
- For the shared deployment model and trigger migration checklist, see [`QuantPlatformKit/docs/deployment_model.md`](../QuantPlatformKit/docs/deployment_model.md).
0 commit comments