Releases: acquia/moonshot
Releases · acquia/moonshot
Beta Release - v2.0.0.beta5
Improvements
- The ASGRollout utility now force-terminates instances after the timeout period, rather than crashing and leaking the instance. (Thanks, @ProZsolt!)
Beta Release - v2.0.0.beta4
New Features
- For Stacks larger than the 51,200 byte limit you can now push your templates to S3 prior to using the create/update commands. (Thanks, @smatyas!)
Improvements
Beta Release - v2.0.0.beta3
New Features
- Added the
CodeDeploySetup
plugin, which can be used to auto-provision the bucket used by CodeDeploy release artifact. (Thanks, @jfarrell!) - The
update
command now supports--refresh-parameters
, which will update stack inputs to match the parent stack outputs even if they have already been set. (Thanks, @jfarrell!) - The
create
andupdate
commands now support a plural form--parents STACK_NAME,STACK_NAME,...
for specifying more than one parent stack. (Thanks, @jfarrell!)
Improvements
- Outputs are now sorted in the
status
command. (Thanks, @pingram3030!) - Added IAM named capability to the CloudFormation calls. (Thanks, @jfarrell!)
- ChangeSet wait time is now configurable in
Moonfile.rb
, and defaults to 90 seconds. (Thanks, @janost!) - CodeDeploy will now attempt to create the required role if it's not found in the account. (Thanks, @jfarrell!)
- The S3BucketViaGitHubRelease artifact mechanism now retries the downloads from GitHub. (Thanks, @borsothy!)
- The GitHubRelease build mechanism now retries waiting for CI status and for the build to exist. (Thanks, @kaushik!)
- Stack status will now output the private IP address for instances which do not have public addresses. (Thanks, @pingram3030!)
- Default stack wait timeout is now 60 minutes. (Thanks, @pdrakeweb!)
Bugfixes
- The backup plugin now correctly backs up the provided answer file, instead of referring to the Moonshot 1.x properties file. (Thanks, @jamesiarmes!)
- The GitHub release build mechanism no longer displays errors while waiting for the release to exist. (Thanks, @pdrakeweb!)
- Full example application is now actually included with compiled .gem artifact. (Thanks, @pingram3030!)
- Stack deletion command will now appropriately return non-zero when stack deletion fails. (Thanks, @ProZsolt!)
Beta Release - v2.0.0.beta2
New Features
- CodeDeploy deployment mechanism now supports adding ASGs that may or may not exist in a given environment. (Thanks, @janost!)
Bugfixes
- Fixed library requires causing
moonshot
CLI tool not to work with Ruby 2.3+. (Thanks, @jfarrell!) - Status command now handles eventual consistency issues between Autoscaling and EC2 APIs, when the EC2 API doesn't return any data about a given instance. (Thanks, @janost!)
- Fixed ssh command for environments with multiple ASGs (Thanks, @janost!)
Beta Release - v2.0.0.beta1
New Features
- Custom commands can now have optional positional parameters. (Thanks, @yitsushi!)
Bugfixes
- Moved
EncryptedParameters
into the plugins module, to align with it's documentation. (Thanks, @janost!) - Backup plugin is now compatible with this release. (Thanks, @borsothy!)
- Fixed a nil dereference when dealing with deployment failures which do not have event diagnostic information. (Thanks, @borsothy!)
Why 2.0?
The interface to the controller's update method changed in a previous beta patch, which breaks what we consider a public interface.
Beta Release - v1.1.0.beta4
Bugfixes
- Fixed an issue where an EC2 instance would fail to be available during an ASGRollout and it would wait forever in state Missing/Missing. Now, it gives up on the failed instance and watches the next one instead. (Thanks, @Skarlso!)
Beta Release - v1.1.0.beta3
Bug Fixes
- Fixed a bug in the KMS Key feature implemented in beta2 where the namespace of the classes were not within
Moonshot
.
Beta Release - v1.1.0.beta2
New Features
- Adds
Moonshot::EncryptedParameters
plugin.
Beta Release - v1.1.0.beta1
New Features
- The ChangeSet API is now used for Update commands. If
--force
or--no-interactive
are not provided, the user will be shown the impact of the update and be asked to approve it. - Moonshot is now aware of the account alias of the AWS account it's being run in. This can be used to specify per-account overrides, such as different S3Bucket instances or parent stacks. It can also be used in custom
Moonshot::Command
subclasses to restrict where a command may be run (e.g. development only commands). - The default location for template files is now
moonshot/template.yml
ormoonshot/template.json
. The previous locations (cloud_formation/APP_NAME.{yml,json}
) are still supported. - The CodeDeploy deployment mechanism now adds
--ignore-app-stop-failures
option topush
anddeploy
commands, which passes the same option to CreateDeployment API in AWS. This can be used when a deployment/rollback leaves instances in a bad state and you want to forcefully deploy a fixed version of an artifact. - A hook system now exists for plugins to add options to existing CLI commands (as used by CodeDeploy above).
Bug Fixes
--show-all-stack-events
now rightly works only on commands it impacts (create
,update
anddelete
).--parent-stack
now works only on commands it impacts (create
andupdate
).--show-all-stack-events
works once again.
Major Release - v1.0.0
After three release candidates, version 1.0.0.rc3 is being promoted to the official 1.0.0 release. Many thanks to everyone who contributed!