Fix a bug in the dev-server where it doesn't pick up the correct secret ARN for the gossip encryption key when the module is configured to generate the gossip key. When var.gossip_encryption_enabled = true the module is supposed to create and use a gossip key. However, when gossip_encryption_enabled = true it was always using the value of var.gossip_key_secret_arn, even if that was unset (which it should be in the case where the key is generated). This caused the creation of the execution role policy to fail because the Resource ARN for gossip key secret was the empty string.
How I've tested this PR:
:eyes:
Using the Lambda registrator acceptance tests (how I found the issue)
Changes proposed in this PR:
Fix a bug in the
dev-serverwhere it doesn't pick up the correct secret ARN for the gossip encryption key when the module is configured to generate the gossip key. Whenvar.gossip_encryption_enabled = truethe module is supposed to create and use a gossip key. However, whengossip_encryption_enabled = trueit was always using the value ofvar.gossip_key_secret_arn, even if that was unset (which it should be in the case where the key is generated). This caused the creation of the execution role policy to fail because theResourceARN for gossip key secret was the empty string.How I've tested this PR:
How I expect reviewers to test this PR:
:eyes:
Checklist: