-
Notifications
You must be signed in to change notification settings - Fork 4k
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
managedPolicyArns on User isn't respected #2557
Closed
FantasticFiasco opened this issue
May 16, 2019
· 2 comments
· Fixed by #3221 or MechanicalRock/tech-radar#14 · May be fixed by MechanicalRock/cdk-constructs#5, MechanicalRock/cdk-constructs#6 or MechanicalRock/cdk-constructs#7
Closed
managedPolicyArns on User isn't respected #2557
FantasticFiasco opened this issue
May 16, 2019
· 2 comments
· Fixed by #3221 or MechanicalRock/tech-radar#14 · May be fixed by MechanicalRock/cdk-constructs#5, MechanicalRock/cdk-constructs#6 or MechanicalRock/cdk-constructs#7
Labels
bug
This issue is a bug.
Comments
+1 from me as I have encountered this bug today, thanks for the information that attachManagedPolicy works. |
Yeah - quite clearly a bug there... That should "just work". Thanks for reporting! |
rix0rrr
added a commit
that referenced
this issue
Jul 5, 2019
Fix adding managed policies to a User upon creation. Fixes #2557. BREAKING CHANGE: `aws-iam.User`: `managedPolicyArns` => `managedPolicies`.
rix0rrr
added a commit
that referenced
this issue
Jul 5, 2019
Fix adding managed policies to a User upon creation. Rename the property for `Group`s. Fixes #2557. BREAKING CHANGE: `aws-iam.User` and `Group`: `managedPolicyArns` => `managedPolicies`.
eladb
pushed a commit
that referenced
this issue
Jul 6, 2019
Fix adding managed policies to a User upon creation. Rename the property for `Group`s. Fixes #2557. BREAKING CHANGE: `aws-iam.User` and `Group`: `managedPolicyArns` => `managedPolicies`.
This was referenced Aug 22, 2019
This was referenced Dec 12, 2019
This was referenced Jan 20, 2020
This was referenced Sep 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Let me start by apologizing if this isn't at all a bug, but instead the expected behavior. You can respond me with a RTFM if that is the case :)
Describe the bug
I thought that specifying a managed policy ARN when creating a
User
would result in the same CloudFormation as when using the methodUser.attachManagedPolicy
.To Reproduce
Lets start with what works.
This will synthesizes into.
The managed policy is attached as expected. Now lets continue with what doesn't work.
This will synthesizes into.
This time there is no attached managed policy, as I'd expect there would be. The managed policy isn't part of the CloudFormation at all.
Expected behavior
Managed policies are not a part of the synthesized CloudFormation if the managed policy is specified when creating the
User
.Version:
The text was updated successfully, but these errors were encountered: