From 9bbc60ca2f97f5e5ad7079517d9c8b5fbd5f34bd Mon Sep 17 00:00:00 2001 From: Solimander Date: Fri, 7 Nov 2025 11:21:59 -0800 Subject: [PATCH] feat: standardize environment variable naming with EIGENX_ prefix --- .../howto/manage-auth-keys/manage-authentication-keys.md | 4 ++-- .../eigencompute/reference/cli-commands/authentication.md | 2 +- .../eigencompute/reference/cli-commands/deployment.md | 2 +- static/eigenx.md | 6 +++--- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/products/eigencompute/howto/manage-auth-keys/manage-authentication-keys.md b/docs/products/eigencompute/howto/manage-auth-keys/manage-authentication-keys.md index e9678457..854738be 100644 --- a/docs/products/eigencompute/howto/manage-auth-keys/manage-authentication-keys.md +++ b/docs/products/eigencompute/howto/manage-auth-keys/manage-authentication-keys.md @@ -17,12 +17,12 @@ When using EigenX, logging in refers to providing your authentication key to the are supported and checked in this order: 1. `--private-key` flag on any command (not recommended). -2. `PRIVATE_KEY` environment variable. +2. `EIGENX_PRIVATE_KEY` environment variable. 3. OS keyring securely stored credentials. :::warning Using the `--private-key` flag to provide your private key directly on the command line is not recommended. When provided on the command line -it may be stored in your shell history. Use the OS keyring to securely store credentials or the `PRIVATE_KEY` environment +it may be stored in your shell history. Use the OS keyring to securely store credentials or the `EIGENX_PRIVATE_KEY` environment variable for CI/CD pipelines. ::: diff --git a/docs/products/eigencompute/reference/cli-commands/authentication.md b/docs/products/eigencompute/reference/cli-commands/authentication.md index 3df7a8a3..43d96d4e 100644 --- a/docs/products/eigencompute/reference/cli-commands/authentication.md +++ b/docs/products/eigencompute/reference/cli-commands/authentication.md @@ -87,7 +87,7 @@ eigenx auth logout [--env ] [--all] Instead of storing your private key in the keyring, you can provide it via environment variable: ```bash -export PRIVATE_KEY=0x1234567890abcdef... +export EIGENX_PRIVATE_KEY=0x1234567890abcdef... eigenx app deploy ``` diff --git a/docs/products/eigencompute/reference/cli-commands/deployment.md b/docs/products/eigencompute/reference/cli-commands/deployment.md index 6fc0b786..675a9e79 100644 --- a/docs/products/eigencompute/reference/cli-commands/deployment.md +++ b/docs/products/eigencompute/reference/cli-commands/deployment.md @@ -236,7 +236,7 @@ eigenx app deploy --dockerfile ./Dockerfile --env-file ./.env ```bash # In CI/CD script -export PRIVATE_KEY=$CI_PRIVATE_KEY +export EIGENX_PRIVATE_KEY=$CI_PRIVATE_KEY docker build --platform linux/amd64 -t registry.io/app:$CI_COMMIT_SHA . docker push registry.io/app:$CI_COMMIT_SHA eigenx app deploy registry.io/app:$CI_COMMIT_SHA diff --git a/static/eigenx.md b/static/eigenx.md index d92c16ff..d244faf1 100644 --- a/static/eigenx.md +++ b/static/eigenx.md @@ -8564,13 +8564,13 @@ var ( RpcUrlFlag = &cli.StringFlag{ Name: "rpc-url", Usage: "RPC URL to connect to blockchain", - EnvVars: []string{"RPC_URL"}, + EnvVars: []string{"EIGENX_RPC_URL"}, } PrivateKeyFlag = &cli.StringFlag{ Name: "private-key", Usage: "Private key for signing transactions", - EnvVars: []string{"PRIVATE_KEY"}, + EnvVars: []string{"EIGENX_PRIVATE_KEY"}, } ForceFlag = &cli.BoolFlag{ @@ -11333,7 +11333,7 @@ eigenx auth logout # Remove key ### 2. Environment Variable ```bash -export PRIVATE_KEY=0x1234... +export EIGENX_PRIVATE_KEY=0x1234... eigenx app deploy ```