Add automatic PagerDuty environment variables to ocm-container

[clcollins]

Summary

This PR automatically passes PagerDuty incident and alert information as environment variables when launching ocm-container via the login feature (pressing l on an incident).

Changes

• New environment variables automatically set in ocm-container:

  • PAGERDUTY_INCIDENT - Contains the PagerDuty incident ID
  • ALERT_DETAILS - Base64 URL-encoded JSON containing the full incident object, all associated alerts, and incident notes

• Implementation:

  • Modified login() function in pkg/tui/commands.go to:
    • Accept incident, alerts, and notes as parameters
    • Serialize incident/alert/notes data to JSON
    • Base64 URL encode the JSON (without padding to avoid parsing issues)
    • Add -e flags to pass environment variables to ocm-container
    • Correctly position env flags after terminal separator and ocm-container command
  • Updated call site in pkg/tui/tui.go to pass incident, alert, and notes data
  • Added alertData struct to encapsulate the data being passed

• Bug Fix:

  • Fixed ocm-container env var parsing error by using base64.RawURLEncoding instead of base64.StdEncoding
  • Standard base64 padding uses = characters which broke ocm-container's parser (splits on = and expects max 2 parts)
  • RawURLEncoding (RFC 4648) eliminates padding while maintaining full data integrity

• Testing:

  • Added comprehensive unit tests in pkg/tui/commands_test.go to verify:
    • JSON serialization of alertData with incident, alerts, and notes
    • Base64 URL encoding without padding characters
    • Data integrity after round-trip encoding/decoding
    • All combinations of incident/alerts/notes (nil, empty, populated)

• Documentation:

  • Updated README.md with new section on automatic PagerDuty environment variables
  • Documented base64 URL encoding usage and rationale
  • Included usage examples for accessing incident, alerts, and notes from within ocm-container

Benefits

• Users can access full incident, alert, and notes details from within ocm-container without manual configuration
• Enables better context awareness during on-call operations
• Allows scripting and automation based on incident data (e.g., extracting cluster details, SOP links, alert severity, previous notes)

Example Usage

Inside ocm-container after login:

# View the incident ID
echo $PAGERDUTY_INCIDENT

# Decode and view the full alert details
echo $ALERT_DETAILS | base64 -d | jq .

# Extract specific alert information
echo $ALERT_DETAILS | base64 -d | jq '.alerts[0].body.details.cluster_id'

# View incident notes
echo $ALERT_DETAILS | base64 -d | jq '.notes'

Technical Details

The ALERT_DETAILS JSON structure:

{
  "incident": { /* full PagerDuty incident object */ },
  "alerts": [ /* array of incident alerts */ ],
  "notes": [ /* array of incident notes */ ]
}

Command structure generated:

gnome-terminal -- ocm-container -e PAGERDUTY_INCIDENT=<id> -e ALERT_DETAILS=<base64> --cluster-id <cluster>

The -e flags are correctly positioned after the terminal separator (--) and the ocm-container command, but before ocm-container's arguments.

Test Plan

• Unit tests pass for alertData serialization (4/4 test cases)
• Binary builds successfully
• All new tests pass
• No = padding characters in base64 output (verified in tests)
• Verified command structure in debug logs
• Tested with live incident - environment variables successfully set in ocm-container

🤖 Generated with Claude Code