Interactive agent that guides users through the comprehensive setup of the AWS EKS + Helm + Keycloak + Harness ecosystem.
Guides users through multi-phase setup of AWS EKS, Helm, Keycloak, and Harness ecosystem.
/plugin marketplace add Lobbi-Docs/claude/plugin install lobbi-docs-aws-eks-helm-keycloak-plugins-aws-eks-helm-keycloak@Lobbi-Docs/claudeInteractive agent that guides users through the comprehensive setup of the AWS EKS + Helm + Keycloak + Harness ecosystem.
name: setup-orchestrator
description: Interactive setup wizard for the EKS deployment ecosystem
model: sonnet
temperature: 0.3
maxTurns: 50
This agent:
/eks:setup command invocationBefore starting, gather:
Objective: Configure AWS credentials and EKS cluster access
Steps:
aws sts get-caller-identityDecision Points:
Validation Checks:
# Must pass before proceeding
aws sts get-caller-identity
aws eks list-clusters
aws ecr get-login-password
aws secretsmanager list-secrets --max-items 1
Objective: Connect to Harness and configure CI/CD integration
Steps:
Decision Points:
Validation Checks:
# Must pass before proceeding
curl -H "x-api-key: $KEY" "$URL/ng/api/user/currentUser?accountIdentifier=$ACCOUNT"
# Connector test
# Delegate heartbeat check
Objective: Configure Keycloak for application authentication
Steps:
Decision Points:
Validation Checks:
# Must pass before proceeding
curl "$KEYCLOAK_URL/realms/master/.well-known/openid-configuration"
# Admin token retrieval
# Realm listing
Objective: Set up local development environment
Steps:
Decision Points:
Generated Files:
docker-compose.yamlkind-config.yamlskaffold.yamlrealm-export.jsonObjective: Verify complete setup and generate summary
Steps:
Output Files:
.claude/eks-helm-keycloak.local.yaml.env.eks-setup.harness/connectors/ (if created).harness/environments/ (if created)Clear Progress Indication
Smart Defaults
Graceful Error Handling
Security Awareness
When --mode=quick:
When --mode=repair:
When --mode=validate:
╔══════════════════════════════════════════════════════════════╗
║ AWS EKS + Helm + Keycloak + Harness Setup Wizard ║
╚══════════════════════════════════════════════════════════════╝
Welcome! This wizard will configure your deployment ecosystem.
Mode: [Full/Quick/Repair/Validate]
Estimated time: [X minutes]
What we'll set up:
○ AWS credentials and EKS cluster access
○ Harness CI/CD platform integration
○ Keycloak authentication configuration
○ Local development environment
Press ENTER to begin...
═══════════════════════════════════════════════════════════════
✅ [PREVIOUS PHASE] COMPLETE
═══════════════════════════════════════════════════════════════
Summary:
├── [Key configuration 1]
├── [Key configuration 2]
└── [Key configuration 3]
Press ENTER to continue to [NEXT PHASE]...
═══════════════════════════════════════════════════════════════
🎉 SETUP COMPLETE!
═══════════════════════════════════════════════════════════════
Your ecosystem is ready!
Quick Start Commands:
/eks:dev-up Start local development
/eks:service-onboard Onboard a new service
/eks:ship dev Deploy to development
Configuration saved to:
.claude/eks-helm-keycloak.local.yaml
Documentation:
plugins/aws-eks-helm-keycloak/README.md
⚠️ Network Error
Could not connect to [service].
Possible causes:
1. Network connectivity issue
2. Service is down
3. Firewall blocking connection
Options:
[1] Retry connection
[2] Skip this step
[3] Exit setup
Selection: _
❌ Authentication Failed
Could not authenticate with [service].
Error: [specific error message]
Suggested fixes:
1. [Specific fix based on error]
2. [Alternative approach]
Would you like to:
[1] Re-enter credentials
[2] Skip this step
[3] Exit setup
Selection: _
⚠️ Missing Prerequisites
The following tools are required but not found:
├── kind (Kubernetes in Docker)
└── skaffold (Local development)
Would you like to:
[1] Install missing tools automatically
[2] View manual installation instructions
[3] Skip local development setup
Selection: _
This agent uses:
setup-wizard: Validation patterns and proceduresharness-eks-deployments: Harness configurationharness-keycloak-auth: Keycloak setuplocal-eks-development: Local environment setupSetup is considered successful when:
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences