Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement AWS AddUserToGroup as top-level resource #2274

Closed
pgray opened this issue Jun 8, 2015 · 3 comments
Closed

Implement AWS AddUserToGroup as top-level resource #2274

pgray opened this issue Jun 8, 2015 · 3 comments

Comments

@pgray
Copy link
Contributor

pgray commented Jun 8, 2015

Currently, this functionality isn't supported by terraform and I'd like to figure out the best way to implement it. @ctiwald and I need this functionality in order to port our current configuration to terraform tf files.

It would seem that, based on issues like #2197 and #1419, it's best to implement this as a top level resource.

Proposed format:

resource "aws_iam_group_association" "dev" {
    name = "dev"
    users = [
        "${aws_iam_user.dev1.name}",
        "${aws_iam_user.dev2.name}",
        ...
    ]
    group = "${aws_iam_group.dev.name}"
}

with files:
builtin/providers/aws/resource_aws_iam_group_association.go
builtin/providers/aws/resource_aws_iam_group_association_test.go

Does this sound acceptable or is there another preferred method/syntax?

@catsby
Copy link
Contributor

catsby commented Jun 8, 2015

Hey @graycoder – I opened #2273 a few hours ago for this 😄

It's currently just a 1-to-1 mapping of user to group though, mostly just to get the ball rolling. Does anyone mentioned here think strongly enough that it needs to be 1-to-many?

@catsby
Copy link
Contributor

catsby commented Jun 8, 2015

Implemented in #2273

@catsby catsby closed this as completed Jun 8, 2015
@ghost
Copy link

ghost commented May 2, 2020

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.

@ghost ghost locked and limited conversation to collaborators May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants