dev-tools.env.example

# dev-tools.env.example — template for ~/.dev-tools.env
#
# Copy to your home directory and fill in your own values:
#
#     cp dev-tools.env.example ~/.dev-tools.env && chmod 600 ~/.dev-tools.env
#
# The `pr-notebook` and `azdo-then-notebook` skills source this file for
# account-specific values. It deliberately lives in $HOME rather than in the
# repo so no account id, ARN, or work identity is ever committed. Nothing here
# is a credential — auth still comes from the `aws` and `databricks` CLI
# profiles — but these values do identify an account, so keep the file local.
#
# Override the location with $DEV_TOOLS_ENV if you keep it elsewhere.

# --- AWS / ECR ---------------------------------------------------------------
# Used to build the registry host and to resolve the PR image's sha256 digest.
AWS_ACCOUNT_ID=000000000000
AWS_REGION=us-east-1
# The `aws` CLI profile with ECR read access in that account.
AWS_ECR_PROFILE=Administrator-000000000000

# --- Databricks --------------------------------------------------------------
# Default `databricks` CLI profile when --profile is not passed.
DATABRICKS_PROFILE=my-profile
# The identity a SINGLE_USER cluster runs as — your Databricks workspace login.
DATABRICKS_SINGLE_USER=you@example.com
# Instance profile the inline cluster assumes.
DATABRICKS_INSTANCE_PROFILE_ARN=arn:aws:iam::000000000000:instance-profile/my-instance-profile
# Secrets Manager ARN exported to the cluster as $SECRETS_ARN.
DATABRICKS_SECRETS_ARN=arn:aws:secretsmanager:us-east-1:000000000000:secret:MY_SECRET-abc123
# Prefix for the inline cluster's name, e.g. "<prefix>:<repo>:<run-slug>".
DATABRICKS_CLUSTER_PREFIX=ci:multi:prod