Expand on github-actions example to build aws resources.
"Easier" - Create ec2 instance, tagged with slack user name/id and other metadata. Send pem back to user once resource is up and stable. Also create status/delete commands to maintain lifecycle of the aws resource.
harder - Same as the easier option, but an eks cluster where the kubeconfig is returned
🤔 Maybe... bashbot gets automatically deployed inside the eks cluster to manage the cluster state and could run commands like:
kubectl get namespaces
kubectl scale --replicas=0 deployment/myapp && sleep 5 && kubectl scale --replicas=1 deployment/myapp
kubectl logs mypod --tail 50
kubectl delete mypod
kubectl set image deployment/frontend www=image:v2
Expand on github-actions example to build aws resources.
"Easier" - Create ec2 instance, tagged with slack user name/id and other metadata. Send pem back to user once resource is up and stable. Also create status/delete commands to maintain lifecycle of the aws resource.
harder - Same as the easier option, but an eks cluster where the kubeconfig is returned
🤔 Maybe... bashbot gets automatically deployed inside the eks cluster to manage the cluster state and could run commands like:
kubectl get namespaceskubectl scale --replicas=0 deployment/myapp && sleep 5 && kubectl scale --replicas=1 deployment/myappkubectl logs mypod --tail 50kubectl delete mypodkubectl set image deployment/frontend www=image:v2