Use shared plugin email alert publisher#75
Conversation
4e5720c to
24f0f1f
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4e5720c95e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| platform_id="longbridge", | ||
| strategy_profile=STRATEGY_PROFILE, | ||
| account_scope=ACCOUNT_REGION, | ||
| service_name=SECRET_NAME, |
There was a problem hiding this comment.
Use runtime service name in alert context label
Build the alert context with the runtime service identity instead of SECRET_NAME; using service_name=SECRET_NAME makes deduplication keys depend on the token secret rather than the deployed service. When multiple deployments share the same strategy/account and secret (for example blue/green or parallel services writing to the same marker store prefix), one service can suppress another service’s alerts as duplicates. The runtime service identity is already available via RUNTIME_SETTINGS.runtime_target/Cloud Run K_SERVICE, so this field should not be set from the secret name.
Useful? React with 👍 / 👎.
Summary
Tests