Skip to content

Introduce SEMGREP_NETWORK_BROKER_PRIVATE_KEY env variable#170

Open
semgrep-jamie wants to merge 1 commit intodevelopfrom
jr/add-SEMGREP_NETWORK_BROKER_PRIVATE_KEY-env-var
Open

Introduce SEMGREP_NETWORK_BROKER_PRIVATE_KEY env variable#170
semgrep-jamie wants to merge 1 commit intodevelopfrom
jr/add-SEMGREP_NETWORK_BROKER_PRIVATE_KEY-env-var

Conversation

@semgrep-jamie
Copy link
Contributor

Allows for the configuration of the wireguard privateKey as an environment variable, $SEMGREP_NETWORK_BROKER_PRIVATE_KEY instead of within the config yaml.

@semgrep-jamie semgrep-jamie self-assigned this Aug 29, 2025
@semgrep-jamie semgrep-jamie requested a review from tpetr as a code owner August 29, 2025 19:40
@semgrep-jamie semgrep-jamie force-pushed the jr/add-SEMGREP_NETWORK_BROKER_PRIVATE_KEY-env-var branch from e25d28a to 9feeb01 Compare February 5, 2026 19:23
@semgrep-jamie semgrep-jamie removed the request for review from tpetr February 5, 2026 19:24
@semgrep-jamie
Copy link
Contributor Author

Since I'll be testing #199 in a lab environment before opening a PR to cut a new release, I figured it was an opportune time to revisit this old PR that I'd raised based on a prospect's suggestion.

I do think that providing an env variable is a nice quality of life improvement that could improve the security of secrets handling for many deployment environments.

I'll test this alongside #199 when I get a chance in a few weeks. In the interim, would love a review and any comments from those tagged!

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