Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/devopsartfactory/goployer
AWS Deployer with Go
https://github.com/devopsartfactory/goployer
aws cicd deployer deployment goployer
Last synced: about 4 hours ago
JSON representation
AWS Deployer with Go
- Host: GitHub
- URL: https://github.com/devopsartfactory/goployer
- Owner: DevopsArtFactory
- License: apache-2.0
- Created: 2020-05-10T02:33:22.000Z (over 4 years ago)
- Default Branch: main
- Last Pushed: 2024-08-29T11:25:37.000Z (3 months ago)
- Last Synced: 2024-11-14T21:43:22.255Z (4 days ago)
- Topics: aws, cicd, deployer, deployment, goployer
- Language: Go
- Homepage: https://goployer.dev
- Size: 93.8 MB
- Stars: 72
- Watchers: 6
- Forks: 13
- Open Issues: 11
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# goployer
`goployer` is an application you can use for EC2 deployment. You can deploy in a blue/green mode. goployer only
changes the autoscaling group so that you don't need to create another load balancer or manually attach autoscaling group to target group.
## Demo
## # Requirements
* You have to create a load balancer and target groups of it which goployer attach a new autoscaling group to.
* If you want to setup loadbalancer and target group with terraform, then please check this [devopsart workshop](https://devops-art-factory.gitbook.io/devops-workshop/terraform/terraform-resource/computing/elb-+-ec2).
* Please understand how goployer really deploys application before applying to the real environment.
## # How goployer works
* Here's the steps that goployer executes for deployment
1. Generate new version for current deployment.
If other autoscaling groups of sample application already existed, for example `hello-v001`, then next version will be `hello-v002`
2. Create a new launch template.
3. Create autoscaling group with launch template from the previous step. A newly created autoscaling group will be automatically attached to the target groups you specified in manifest.
4. Check all instances of all stacks are healty. Until all of them pass healthchecking, it won't go to the next step.
5. (optional) If you add `autoscaling` in manifest, goployer creates autoscaling policies and put these to the autoscaling group. If you use `alarms` with autoscaling, then goployer will also create a cloudwatch alarm for autoscaling policy.
6. After all stacks are deployed, then goployer tries to delete previous versions of the same application.
Launch templates of previous autoscaling groups are also going to be deleted.
## # Spot Instance
* You can use `spot instance` option with goployer.
* There are two possible ways to use `spot instance`.
`instance_market_options` : You can set spot instance options and with this, you will only use spot instances.
```yaml
instance_market_options:
market_type: spot
spot_options:
block_duration_minutes: 180
instance_interruption_behavior: terminate # terminate / stop / hibernate
max_price: 0.2
spot_instance_type: one-time # one-time or persistent
```
`mixed_instances_policy` : You can mix `on-demand` and `spot` together with this setting.
```yaml
mixed_instances_policy:
enabled: true
override_instance_types:
- c5.large
- c5.xlarge
on_demand_percentage: 20
spot_allocation_strategy: lowest-price
spot_instance_pools: 3
spot_max_price: 0.3
```
You can see the detailed information in [manifest format](https://goployer.dev/docs/references/manifest/) page.
## Examples
* You can find few examples of manifest file so that you can test it with this.
```bash
cd examples/manifests
```