Added support for same region replicas.

[jstojanovski-scwx]

Hi there... This fixes the fault I see with #2

Be gentle- It's my first PR for a terraform module. :)

[aknysh]

@jstojanovski-scwx thanks!
please run terraform fmt on all files, CI/CD is failing

[aknysh]

Suggested change

	count = "${local.enabled && length(var.kms_key_id) == 0 && !var.same_region ? 1 : 0}"
	count = "${local.enabled && length(var.kms_key_id) == 0 ? 1 : 0}"

I don't think we need to control the KMS key by var.same_region because if var.same_region = true, you always have to specify var.kms_key_id because of this expression

kms_key_id                = "${length(var.kms_key_id) > 0 ? var.kms_key_id : join("", aws_kms_key.default.*.arn)}"

but maybe a user needs to create a new key in the same region as the master instance (which let's say was created w/o a key)

[aknysh]

Suggested change

	count = "${local.enabled && !var.same_region ? 1 : 0}"
	count = "${local.enabled && var.same_region == "false" ? 1 : 0}"

Since var.same_region is a string, not boolean

[aknysh]

thanks @jstojanovski-scwx
Looks good, just a few comments.
And after you address the comments, please run terraform fmt to format all TF files, and then rebuild README by executing these command:

make init
make readme/deps
make readme

This will add the new variable to README.md

[jwhitcraft]

Any update on getting the suggestions fixed @jstojanovski-scwx ?

If you don't have time, I can make the changes and push them to your branch.

[jstojanovski-scwx]

@jwhitcraft Apologies... We stopped using this module, which meant it's fix priority dropped (for me). As a result, I haven't had the time to swing back around to fix it... If you have the cycles, please feel free. Otherwise, I'll get to it (just not for a while yet).