customize global_replication_group_id_suffix argument

[adubkov]

Is your request related to a new offering from AWS?

Is this functionality available in the AWS provider for Terraform?
Yes ✅: The ability to name the global_replication_group_id_suffix custom argument is supported in the AWS provider for Terraform.

Is your request related to a problem? Please describe.

Currently, when creating a global datastore with this module, the global datastore name is always generated to match the replication group name. This makes it impossible to assign a custom name for the global datastore that differs from the replication group name.

For example, with the current setup:

my-global-datastore-east-1:
 - my-global-datastore-us-east-1
 - my-global-datastore-us-west-1

It is not possible to rename the global datastore separately from the replication group. The replication group name is directly used as the suffix for global_replication_group_id_suffix.

Describe the solution you'd like.

I would like the ability to set a custom value for the global_replication_group_id_suffix argument, so that the name of the global datastore is independent of the replication group name.

For example:

global-datastore:
 - my-global-datastore-us-east-1
 - my-global-datastore-us-west-1

Here, global-datastore would be the global datastore name, while the replication group names remain separate.

Describe alternatives you've considered.

Currently, there does not appear to be a way to achieve this functionality with the current version of the module. If such a feature is already implemented but undocumented, guidance on enabling it would suffice as an alternative.

Additional context

This feature would provide more flexibility for managing global datastores, especially for organizations that require naming conventions or separation between global datastore names and replication group names. This change would also improve clarity and manageability of resources in AWS environments with multiple global datastores.

[adubkov]

@bryantbiggs why is this closed?

[bryantbiggs]

Th information requested on the issue template is there for a reason

[adubkov]

here we go, thanks to chatgpt

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.