hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.81k stars 9.16k forks source link

Create Resources and Data Sources for User Groups and Users Redis 6.X RBAC #16327

Closed drarnold closed 3 years ago

drarnold commented 3 years ago

Community Note

Description

Please incorporate the functionality of adding/updating/removing user groups and users for the redis elasticache integration.

New or Affected Resource(s)

Impacted Existing Resources

Impacted Existing Data Sources

Impacted New Resources

Impacted New Data Sources

Potential Terraform Configuration

Will need fully developed resources and data sources for this feature request.

References

ewbankkit commented 3 years ago

Related:

HaroonSaid commented 3 years ago

Any Updates?

drarnold commented 3 years ago

Hey @HaroonSaid I was actually going to start working on this pull request during my company's Hackathon since this will be something that we will need in the future. Not sure if anyone is working on it from the Hashicorp side, but willing to work with someone to get this pushed out for usage.

bill-rich commented 3 years ago

User and user group PRs have been merged

jamesglennan commented 3 years ago

Am I right in understanding that the above code merge allows the creation of user and usergroups but doesn't allow us to create an association between a usergroup and an elasticache cluster yet? If this is the case, should this be filed in a separate issue or re-open this one?

ramekin commented 3 years ago

@jamesglennan - I am not seeing a way to associate a usergroup with the cluster either. I just went down the path of creating some users and a usergroup and realized there was still that last manual step.

jamesglennan commented 3 years ago

@ramekin I have created another issue https://github.com/hashicorp/terraform-provider-aws/issues/20328 I have some code that i need to test out to implement this, however note this will only affect the replication_group resource (as opposed to the cluster resource) because of limitation on aws side- their api and go-sdk only support this on replication_group resources

I'm still fuzzy on the real difference, but as i understand one is more for memcache the other more for redis? So i guess it makes sense why usergroups arent supported.

github-actions[bot] commented 3 years ago

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.