# View RT enablement status
tdx ps view <parent_segment_id> --json

# Expected response when enabled:
# {
#   "realtime_enabled": true,
#   "realtime_config_exists": true,
#   "status": "enabled"
# }

# When not enabled:
# {
#   "realtime_enabled": false,
#   "message": "Contact CSM to enable RT 2.0"
# }

Subject: Request to Enable RT 2.0 for Parent Segment

Please enable RT 2.0 (Real-Time Personalization) for:

**Parent Segment Details:**
- Parent Segment ID: <id>
- Parent Segment Name: <name>
- Region: <region>
- Environment: production

**Use Case:**
[Describe your RT 2.0 use case: triggers, personalization, or both]

**Requirements:**
- Enable RT 2.0 feature
- Provide Reactor Instance ID
- Confirm enablement completion

# Option 1: Initialize new configuration template
tdx ps pz init <parent_segment_id> -o rt_config.yaml

# This creates a YAML template with:
# - Sample event tables
# - Example RT attributes
# - ID stitching configuration
# - Batch attribute imports

# Option 2: View existing configuration
tdx ps view <parent_segment_id> --json

# Option 3: Set parent segment context
tdx ps use <parent_segment_id>

# Now commands default to this parent segment:
tdx ps pz init -o rt_config.yaml
tdx ps view

parent_segment_id: "394649"

# Event tables - Configure with rt-config-events skill
events:
  - name: "page_view"
    database: "events_db"
    table: "web_events"
    filter:
      field: "td_path"
      pattern: "^/pageview/"

# RT attributes - Configure with rt-config-attributes skill
attributes:
  - name: "last_product_viewed"
    type: "single"
    source_event: "page_view"
    source_field: "product_id"

# ID stitching - Configure with rt-config-id-stitching skill
id_stitching:
  primary_key: "td_client_id"
  stitching_keys:
    - name: "td_client_id"
    - name: "email"

# List databases
tdx databases --json

# List tables in database
tdx tables list <database_name> --json

# View table schema
tdx table describe <database_name> <table_name>

# Preview table data
tdx query "select * from <database>.<table> limit 10"

# Check existing parent segment attributes (batch layer)
tdx ps view <parent_segment_id> --json | jq '.attributes'

# List all parent segments
tdx ps list --json

# Validate YAML syntax
tdx ps rt validate rt_config.yaml

# Common validation checks:
# - parent_segment_id exists
# - Event tables are accessible
# - Attribute names are unique
# - primary_key is in stitching_keys
# - Regex patterns are valid

# Push to Treasure Data
tdx ps push rt_config.yaml

# Monitor push status
tdx ps view <parent_segment_id> --json | jq '.realtime_config.status'

# Status values:
# - "ok" - Configuration active
# - "updating" - Push in progress
# - "error" - Configuration failed

# Verify RT configuration
tdx ps view <parent_segment_id> --json

# Open in browser
tdx ps view <parent_segment_id> --web

# Check specific components
tdx ps view <parent_segment_id> --json | jq '.realtime_config.events'
tdx ps view <parent_segment_id> --json | jq '.realtime_config.key_columns'

# Pull current config (not yet available in tdx)
# Use API to view current state
tdx ps view <parent_segment_id> --json

# Make changes to YAML file
# Push updated configuration
tdx ps push rt_config.yaml

# Note: Some updates require API calls
# See rt-config-events, rt-config-attributes skills for API updates