Shelter Kitties
Adoption Enhancements
AWS is now supported. Resource types implemented: VPC, FirewallRule, User, Group, Role, Log, Server. Partial progress has been made on other AWS resource types.
The --stubdeploy option now defaults to false.
Minimization of generated Baskets of Kittens is now more complete. BoKs generated by adoption should be significantly more terse.
Deploy-specific log files
Logger and Chef output pertaining to specific deploys is now duplicated into a file named log in each deployment directory.
Fargate with EKS
AWS EKS is now supported with Fargate, in lieu of using managed worker nodes. This is now the default behavior when building when flavor is set to Fargate and no ECS containers are declared.
AWS IAM Improvements
Directly-attached and inline IAM policies now exposed to users and groups, and roles now support conditions in their can_assume blocks.
Quality-of-Life Enhancements
- There is now a
monitoringflag that can be set onserversandserver_poolsto explicitly enable/disable Chef/Nagios based monitoring of a host. - AWS NAT Gateways should now be tagged
mu-cleanupwill behave more gracefully when an underlying resource implementation throws an error- AWS Security Groups can now use our standardized reference schema to reference one another; references in general should be behave more reliably.
Automated testing
Added mu-run-tests utility, which runs through the Basket of Kittens library in modules/tests for improved API test coverage, currently at 25 tests. Invoked without arguments, it will conduct a simple parse test of each; with the --full argument it will deploy and clean up each in turn.
Bugfixes
- Correctly handle cross-region AWS peering
- Google VPCs should no longer generate conflicting subnet names
- Cleanup of nonexistent Chef Vaults specified in deploy metadata should no longer cause failures