Skip to content

feat(#10): add --no-proxy global flag to bypass proxy configuration - #11

Open
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/10-no-proxy-flag
Open

feat(#10): add --no-proxy global flag to bypass proxy configuration#11
fullsend-ai-coder[bot] wants to merge 1 commit into
mainfrom
agent/10-no-proxy-flag

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown

Allow developers to override the configured proxy in backplane-cli without editing local config files, enabling easier testing against locally running backplane-api instances.

The --no-proxy flag is added as a global persistent flag available to all subcommands (login, remediation, session). When set, it takes precedence over both the --proxy flag and any proxy configured in the backplane config file or HTTPS_PROXY environment variable.


Closes #10

Post-script verification

  • Branch is not main/master (agent/10-no-proxy-flag)
  • Secret scan passed (gitleaks — ae64d7cf510a866657b8dcb2881b8c7dc3fe2a16..HEAD)
  • Pre-commit hooks passed (authoritative run on runner)
  • Tests ran inside sandbox

Allow developers to override the configured proxy in backplane-cli
without editing local config files, enabling easier testing against
locally running backplane-api instances.

The --no-proxy flag is added as a global persistent flag available to
all subcommands (login, remediation, session). When set, it takes
precedence over both the --proxy flag and any proxy configured in the
backplane config file or HTTPS_PROXY environment variable.

Closes #10
@samanthajayasinghe

Copy link
Copy Markdown
Owner

/fs-retro

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.

[RFE] Backplane-cli should have a no-proxy flag

1 participant