Add create global cluster with rds cluster role

[mandar242]

SUMMARY

Continuing on PR #79

Add role create_rds_global_cluster to create aurora global cluster with two different region rds clusters.

Currently, RDS resources created by role will be connect to Default VPC of the specified region.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

create_rds_global_cluster

[mandar242]

Waiting on ansible-collections/amazon.aws#1705

[SCLogo]

does it mean currently we can create Global database only in the same region?

[GomathiselviS]

There are a few ansible-lint issues that need to be addressed, but aside from those, the role functions properly.

[hakbailey]

There are a few typos noted inline, but I also have a general comment about region. When I try to test this locally, it's picking up the aws region from test config in the Create a primary cluster for global database step of create.yaml, with a warning that Both option region and its alias aws_region are set. I think we either need to pass aws_region instead of region to the calls to amazon.aws modules, or we need to set the aws_region variable explicitly to match region. This will be an issue outside of testing for users if they have the AWS region set in ENV since the aws_setup_credentials role pulls from that to set the aws_region value.

[mandar242]

this issue is not being reproduced in my testing, role works as expected, not sure if I'm missing anything
for reference, my ~/.aws/credentials looks like below

Hmm. I'm running into the same issue when calling this role from the new high availability webapp playbook too. In that case aws_access_key, aws_secret_access_key, and aws_region variables are passed directly to the playbook via a credentials file (and aws_region is required) so I think we need to make sure region and aws_region match here.

[hakbailey]

Just a couple more comments otherwise this looks good!