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.

Sign up for GitHub

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

Jump to bottom

aws.iam.*PolicyAttachmentArgs inconsistencies #808

Closed
ncsibra opened this issue Nov 29, 2019 · 0 comments · Fixed by #809
Closed

aws.iam.*PolicyAttachmentArgs inconsistencies #808

ncsibra opened this issue Nov 29, 2019 · 0 comments · Fixed by #809
Assignees
@stack72
Labels
area/providers impact/usability Something that impacts users' ability to use the product easily and intuitively
Milestone
0.30

Comments

@ncsibra
Copy link

ncsibra commented Nov 29, 2019

Hi,

aws.iam.RolePolicyAttachmentArgs requires the role as a pulumi.Input<string | Role>, but GroupPolicyAttachmentArgs, UserPolicyAttachmentArgs and PolicyAttachmentArgs accepts only their respective class e.g. pulumi.Input<Group>, pulumi.Input<User> and does not accept string, which makes hard to use them when those resources are managed outside pulumi, so we only have a name or id.
Especially because the aws.iam.get* functions does not return these types, but Get*Results, e.g. GetGroupResults.
Would be nice to make them similar like the RolePolicyAttachmentArgs.
@ncsibra ncsibra changed the title IAM .*PolicyAttachment inconsistencies aws.iam.*PolicyAttachmentArgs inconsistencies Nov 29, 2019
stack72 added a commit that referenced this issue Dec 1, 2019
@stack72
Allow use of string or Type in IAM PolicyAttachment resources
2a0f68c 
Fixes: #808
@stack72 stack72 mentioned this issue Dec 1, 2019
Merged
stack72 added a commit that referenced this issue Dec 1, 2019
@stack72
Allow use of string or Type in IAM PolicyAttachment resources
f39e15b 
Fixes: #808
@stack72 stack72 added area/providers impact/usability Something that impacts users' ability to use the product easily and intuitively labels Dec 1, 2019
@stack72 stack72 added this to the 0.30 milestone Dec 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stack72 stack72

Labels
area/providers impact/usability Something that impacts users' ability to use the product easily and intuitively
Projects
None yet
Milestone
0.30
Development

Successfully merging a pull request may close this issue.

Allow use of string or Type in IAM PolicyAttachment resources pulumi/pulumi-aws
2 participants
@stack72 @ncsibra