Yusuke Kuoka

I'm interested in this feature, too 👍 Would this be in line with the direction maintainers want to go? If so, I'm eager to contribute anything I can. FWIW, I...

@jessesuen Hey!! Thank you so much for your detailed comment. > we actually started off using the Kubernetes Deployment controller codebase. There was a lot of code-reused from there. Ahh...

@jessesuen Thanks for your confirmation! > Plus I imagine would be very error prone. So I do believe our only option would be to manage the node labels for canary...

@jessesuen Would you mind if I submitted a huge pull request to refactor it to extract out the `Deployer` interface to abstract away most of replicaset-related code? Here's the whole...

> IMHO.. gigantic refactor with a big risk of introducing behaviours that eventually may affect the project. But with enough tests and a fleet big enough where both Deployments and...

Oh, note that I imagine there will be two flavours of STS support :) One flavour would deploy two or more statefulsets and do blue-green or canary releases across those....

Thanks for sharing this 👍 FYI, I've forked this repo and on top of mikepii's work, managed to support v2. https://github.com/mumoshu/cloudformation-docker-registry

I encountered this too. For me, running `terraform plan` against the the tf file and the tfstate generated by terraforming shows a bunch of removal/addition of equivalent sg rules due...

Perhaps relevant: https://github.com/hashicorp/terraform/issues/670#issuecomment-178044999 and https://github.com/hashicorp/terraform/issues/2843#issuecomment-258379279

I can consistently reproduce my problem by running: ``` for i in $(seq 5); do bundle exec terraforming s3 > $i.tf && bundle exec terraforming s3 --tfstate > $i.tfstate &&...