Hotfix

Goployer occurs error if there is no api_test_templates which is not required for all manifest.
This is fixed in 2.0.6

And there is one minor change

• Allow value 0 for onDemandPercentage in mixedInstancesPolicy, which means provisioning spot instance only.

2.0.5 Release

Release Note

• Support io2 volume type. #103

• Add iops configuration in the manifest file for supporting iops-required volume type #103

• Add alias of log-level with v. Any command could be used with -v info|debug|warning.... Default value of log is changed from info to warning #103

• Add security group information in goployer status command #105

• add on_demand_base_capacity in MixedInstancesPolicy #106

• change slack/logging format #106

• add vegeta for api testing (beta version) #106

2.0.4 Release

• Apply clean code #93
• Add scheduled action #85
• Fix autoscaling group alarm action bug #101
• Change goployer status format #97
• Apply default region for goployer status and update command if there is no --region option #93

2.0.3 Minor Release

Minor release

• doHealthchecking multi-thread error fix
• Currently goployer gathers only 1 day because of wrong comparison.
• If the number of current instances is larger than that in manifest, then it will follow the larger one. But when do healthchecking, this is not applied..
• add goployer update command

Hotfix

Hotfix

• change script path in init manifest file.
• if no metrics.yaml file exists, then consider it as disabled.

Add more useful command and features

• Add goployer add command for users to add manifest file
• Add SLACK_WEBHOOK_URL environment variable
• deprecate ansible_tags and add tags configuration for a single stack

2.0.0 Major Release

We adopted command line interface format for goployer

Command lines:

• goployer init : create files for goployer project
• goployer deploy : deploy a new application
• goployer delete : delete previous version of application

Now we have three common commands for utilizing goployer as deployment tool.
We are going to add more features

https://goployer.dev

Update release

• Fix bugs
  • change versioning calculation 100 -> 1000
• add request count metrics

First major version

First Release

Safe Deployment with versioning

Blue/Green Deployment

• Goployer uses blue/green deployment by default in order to ensure the safe deployment. Goployer will create new autoscaling group and attach it to the target group. After checking all the instances of autoscaling group are healthy, then delete the previous autoscaling group.
• Versioning - In the autoscaling group name, you can find the current version easily.

Use most of autoscaling group feature

Autoscaling Policy

• You can create autoscaling policy with AWS CloudWatch.

Spot Instance

• You can make launch template with spot configuration.

Mixed Instance Policy

• You can use on-demand and spot instance together with MixedInstancePolicy supported by autoscaling group. Autoscaling group will control spot request on behalf of you.

Metric Enabled

History Management

• You can make history records to AWS DynamoDB and keep track of deployment duration.
  Demo