v1.0.0 Disruptive change

This is the first release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature modules.

It contains a disruptive change. See #27 for details, but the short story is that applying this update will likely cause Terraform to delete and re-create the EKS IAM role. This may cause a transient disruption in service, but it should be within the normal tolerance for delays in recovering from an expired session.

More significantly, if you have attached additional policies to the role created by this module, those policies will need to be re-attached to the re-created role. (We expect that very few people are actually doing this.)

Refactor enable logic to use counts instead of `for_each` @elventear (#27)

what

Use count instead of for_each to manage if a resource is enabled or disabled.

why

If any element of the service account name is not known at plan time, for_each would cause the plan to fail.

The main advantage of for_each over count is stability when an item in a list is added or removed or the order of elements in a list changes. With for_each, only the changed item is affected, while with count other items can be affected by being moved to a different position in the list. This advantage is not applicable to this module because there is always only one item.

note

This change will cause the IAM role to be deleted and recreated. If you have attached policies to the role outside of this module, you will need to reattach them.