Support three protected manual IBKR facts publication targets - #562
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Add three fixed manual targets to the existing single-report publisher. Each selected target is resolved from protected configuration, with strict identity, destination, prefix and primary-account duplicate checks. The existing default scheduled target remains unchanged.
Prepare only the two project variables before cloud authentication, mask their values, and preserve primary identity settings for the second process. The publisher keeps the existing complete report/source/revision/native identity and freshness checks and sends at most one POST. Exact-report manual publication skips unrelated heartbeat work.
Validation
No additional sampling, schedule changes, trading activation or new credentials/IAM. Protected configuration and real publication are verified separately.