-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Documentation needs improvement (!) #529
Comments
@bryantbiggs any comment? |
I'm not sure what to comment here - it seems like you are not familiar with some of the Terraform module norms and conventions so I would suggest first digging into the Terraform documentation and then starting to look at modules, and then module implementations (not just ours, there are many modules out there and some really well written ones on the registry) |
Maybe there are, but the one I am referring to [1] is not. The documentation is pretty much non-existant and what exists partially does not makes sense. Hence I think it can be improved. So why not keep this ticket open and make things better? [1] |
but what I think you are actually looking for is
|
Thanks for the link, but I still don't see how that addresses my original points. E.g. pick my Can you explain what |
It determines whether a role is created or not |
but the whole purpose of the module is to create a role: |
Trying to create a role with a "federated" principal. Seems impossible.
This needs an example:
https://registry.terraform.io/modules/terraform-aws-modules/iam/aws/latest/submodules/iam-assumable-role-with-oidc
Trying to use it like this:
resource "iam-assumable-role-with-oidc" "github_actions_eks_role" { .. }
, runningtf init
results in:Same issue for
resource "iam_iam-assumable-role-with-oidc" "github_actions_eks_role" { .. }
All links on the fields just link to itself. e.g. this one. That's not helpful.
Why is there a boolean variable whether to create a role or not (
create_role
)? The whole purpose is to create a role. Doesn't make sense to me.What is the purpose of specifying the number of attached policies (number_of_role_policy_arns)? Also doesn't make sense to me. Should just count itself based on # attached policies.
A lot of the other fields are not self-explanatory (e.g. role_path - why is that required?). A simple example how to use would be so much more user friendly.
The text was updated successfully, but these errors were encountered: