generated from pulumi/pulumi-tf-provider-boilerplate
-
Notifications
You must be signed in to change notification settings - Fork 7
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
GetAwsCrossAcountPolicy missing "iam:ListInstanceProfiles" permission #21
Labels
kind/bug
Some behavior is incorrect or out of spec
Comments
simonkarman
added
kind/bug
Some behavior is incorrect or out of spec
needs-triage
Needs attention from the triage team
labels
Aug 11, 2022
I understand that this probably needs to be fixed in the underlying terraform provider, and I'm happy to assist with this. |
Thanks for the report @simonkarman! I didn't see any related open issues upstream, so this will need some further investigation to narrow down the problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
The GetAwsCrossAcountPolicy generates a policy you can use for the workspace, this policy is then used by the workspace to create clusters, however when specifying
PassRoles
in the GetAwsCrossAccountPolicyArgs (indicating that you're using instance profiles), the outputted policy is missing the "iam:ListInstanceProfiles" permission.Steps to reproduce
where passRoles has type
pulumi.StringArrayInput
Expected Behavior
I expect the resulting policy to contain the "iam:ListInstanceProfiles" permission when the
PassRoles
property is non empty.Actual Behavior
The resulting policy does NOT contain the "iam:ListInstanceProfiles" permission when the
PassRoles
property is non empty.Versions used
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: