You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a lazy developer who wants to automate continuous deployment of myapp to Kubernetes clusters, while not wanting to spend much time on learning yet another deployment tool(s), I want an easy way to turn any deployment command to CodeDeploy-ready.
How it should work
You just prefix your deployment command with kodedeploy FLAGS -- and CodeDeploy persists and (re)plays your command whenever necessary.
More concretely, once you run kodedeploy -- CMD, it creates:
A CodeDeploy application (if missing)
A CodeDeploy revision for the application
A CodeDeploy deployment group (if missing)
A CodeDeploy deployment in the group
Each revision is stored inside a S3 bucket, containing following files:
An auto-generated appspec.yml, before-install.sh, and after-install.sh
Everything inside the current working directory, so that it can be used from within the CodeDeploy deployment script
As a lazy developer who wants to automate continuous deployment of myapp to Kubernetes clusters, while not wanting to spend much time on learning yet another deployment tool(s), I want an easy way to turn any deployment command to CodeDeploy-ready.
How it should work
You just prefix your deployment command with
kodedeploy FLAGS --
and CodeDeploy persists and (re)plays your command whenever necessary.More concretely, once you run
kodedeploy -- CMD
, it creates:Each revision is stored inside a S3 bucket, containing following files:
appspec.yml
:before-install.sh
:after-install.sh
:Usage examples
With kubectl
$ kodedeploy apply --namespace myapp --environment preview -- kubectl apply -n myapp -f deploy/kubernetes
With helm
$ kodedeploy apply --namespace myapp --environment preview -- helm upgrade charts/myapp --name myapp --tiller-namespace myapp --namespace myapp
With helm-tiller
$ kodedeploy apply --namespace myapp --environment preview -- helm tiller run myapp -- upgrade charts/myapp --name myapp --namespace myapp
The text was updated successfully, but these errors were encountered: