# AWS Configuration for Integration Tests
# These credentials must have permissions to manage users in the specified Cognito User Pool

# AWS Region where your Cognito User Pool is located
AWS_REGION=us-east-1

# AWS Credentials
# Option 1: Use IAM user credentials
AWS_ACCESS_KEY_ID=your_access_key_here
AWS_SECRET_ACCESS_KEY=your_secret_key_here

# Option 2: Use temporary credentials (SSO/STS)
# AWS_SESSION_TOKEN=your_session_token_here

# Cognito Configuration
COGNITO_USER_POOL_ID=us-east-1_XXXXXXXXX

# Optional: Cognito Client ID if needed for JWT generation
# COGNITO_CLIENT_ID=your_client_id_here

# 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

# 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=your_project_id_here

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

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

# Optional: Permit.io Base URL (defaults to https://api.permit.io)
# PERMIT_IO_BASE_URL=https://api.permit.io

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

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

# Domain for test user emails
TEST_USER_DOMAIN=example.com

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