Skip to content

Support multi-target gateway deploy workflow - #58

Merged
Pigbibi merged 1 commit into
mainfrom
codex/multi-target-gateway-github-deploy
May 28, 2026
Merged

Support multi-target gateway deploy workflow#58
Pigbibi merged 1 commit into
mainfrom
codex/multi-target-gateway-github-deploy

Conversation

@Pigbibi

@Pigbibi Pigbibi commented May 28, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • add target selection to the deploy workflow using IB_GATEWAY_TARGETS_JSON
  • support sequential deploys across multiple gateway projects/VMs via GitHub OIDC
  • allow non-2FA gateway targets by only requiring TOTP when auto-fill is enabled
  • document the generic multi-target configuration pattern without real credentials

Verification

  • git diff --check
  • configured IB_GATEWAY_TARGETS_JSON repo variable with u15998061/u16608560/u18336562 target keys
  • created GitHub OIDC deploy service accounts for the u15998061 and u16608560 projects
  • copied u15998061/u16608560 runtime credentials into each project's Secret Manager without printing secret values

@Pigbibi
Pigbibi force-pushed the codex/multi-target-gateway-github-deploy branch from 32646c9 to 3c28afb Compare May 28, 2026 07:14
@Pigbibi
Pigbibi merged commit 8738b37 into main May 28, 2026
1 check passed
@Pigbibi
Pigbibi deleted the codex/multi-target-gateway-github-deploy branch May 28, 2026 07:14

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 32646c981e

ℹ️ 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".

Comment on lines +370 to +372
twofa_autofill="$(printf '%s' "${IBKR_2FA_AUTOFILL:-}" | tr '[:upper:]' '[:lower:]')"
if [ "${twofa_autofill}" = "yes" ] || [ "${twofa_autofill}" = "true" ] || [ "${twofa_autofill}" = "1" ]; then
required_values+=(totp_secret)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Treat omitted autofill as requiring TOTP

When IBKR_2FA_AUTOFILL is omitted for a target, this condition skips adding totp_secret to the required values, but the generated .env leaves the variable empty and docker-compose.yml defaults IBKR_2FA_AUTOFILL to yes via ${IBKR_2FA_AUTOFILL:-yes}. In that default configuration, 2fa_bot.py exits if TOTP_SECRET is missing, so scheduled/push deploys can now pass validation and install a gateway whose 2FA helper immediately fails. Please either treat an empty autofill value as enabled here or explicitly default the emitted value to no for non-TOTP targets.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant