# AWS Configuration for Integration Tests
# These credentials must have permissions to manage users in the specified Cognito User Pool
#
# IMPORTANT: When running from devbox shell, the following vars are set for LocalStack
# and MUST be unset to reach real AWS:
#   AWS_ENDPOINT_URL=http://localhost:4566  (routes all calls to LocalStack)
#   AWS_ACCESS_KEY_ID=test                  (fake LocalStack credential)
#   AWS_SECRET_ACCESS_KEY=test              (fake LocalStack credential)
#
# Use this command prefix to override them:
#   env -u AWS_ACCESS_KEY_ID -u AWS_SECRET_ACCESS_KEY -u AWS_SESSION_TOKEN -u AWS_ENDPOINT_URL \
#     AWS_REGION=us-east-2 AWS_PROFILE=aarete \
#     go test -tags=integration -v -count=1 -timeout=300s ./test/integration/...

# AWS Region where Cognito User Pool is located (us-east-2 for aarete)
AWS_REGION=us-east-2

# Cognito Configuration
COGNITO_USER_POOL_ID=us-east-2_21upuTkkT

# Suppress Cognito welcome emails to avoid hitting the 50 emails/day limit
# Set to "true" for integration tests, leave unset or set to "false" for production
COGNITO_SUPPRESS_EMAILS=true

# Optional: Scopes user operations to a specific environment within the shared Cognito pool.
# Used by EnvFilter integration tests. When set, admin operations only see users tagged
# with this environment ID (or untagged legacy users). Leave empty/unset for unscoped mode.
# COGNITO_ENVIRONMENT_ID=testenv

# Skip Permit.io cleanup after tests (useful for manual inspection of created users)
# Set to "true" to leave users in Permit.io after tests complete
# Remember to manually delete test users afterward to avoid clutter
SKIP_PERMITIO_CLEANUP=false

# Permit.io Configuration
# Get these from your Permit.io dashboard

# Permit.io API Key (starts with "permit_key_")
PERMIT_IO_API_KEY=permit_key_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

# Permit.io Project ID
PERMIT_IO_PROJECT_ID=default

# Permit.io Environment ID (e.g., "dev", "staging", "production")
PERMIT_IO_ENV_ID=dev

# Permit.io Tenant (usually "default")
PERMIT_IO_TENANT=default

# Test Configuration
# These control how test user emails are generated

# Prefix for test user emails (helps identify test users)
TEST_USER_EMAIL_PREFIX=int-test-

# Domain for test user emails
TEST_USER_DOMAIN=example.com

# Example: With the above settings, test users will have emails like:
# int-test-create-1697123456@example.com