Morgante Pell

One possible fix would be to split node pools into two different resources: one for linux node pools and one for Windows node pools, with the latter dependent on the...

It's still on our backlog, but don't have a timeline. If someone wants to pick it up in the meantime, I'd be happy to review a pull request.

I agree this is annoying currently, but unfortunately there isn't an easy solution with Terraform Core currently. Terraform is working on adding optional attribute support for objects: https://www.terraform.io/docs/language/expressions/type-constraints.html#experimental-optional-object-type-attributes Once that...

If you want to lock down access entirely, you can use the cluster CIDR in the master authorized networks list.

Since this is solved, I'm not sure we need to do anything to fix in this module.

Got it, yes we could update the README. I'm happy to review a PR.

It's ad hoc, would be happy to review PRs migrating them over but we don't generally proactively prioritize it.

This *should* be working in 6.0. @robbieheywood Do you mind sharing a configuration where this is breaking?

Have you tried setting the value to `null`? Like this: ``` additional_users = [{name: "test", password: null}] ```

Interesting, this is definitely a bug then. `null` should be sufficient to accept the default. We'll put it on the queue, but would also be happy to review a PR.