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

Add "name_with_path" to iam_role data source and resource #6287

Closed

Conversation

rehevkor5
Copy link
Contributor

Changes proposed in this pull request:

Add "name_with_path" to iam_role data source and resource

  • Provides the "friendly name" plus the path without leading slash,
    which in some cases must be used instead of "id"/friendly name when the
    role has a non-default path (anything but "/").

Output from acceptance testing:

Not run (sorry).

- Provides the "friendly name" plus the path without leading slash,
which in some cases must be used instead of "id"/friendly name when the
role has a non-default path (anything but "/").
@ghost ghost added size/S Managed by automation to categorize the size of a PR. documentation Introduces or discusses updates to documentation. service/iam Issues and PRs that pertain to the iam service. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. labels Oct 26, 2018
@bflad bflad added the enhancement Requests to existing resources that expand the functionality or scope. label Oct 28, 2018
@bflad
Copy link
Contributor

bflad commented Oct 30, 2018

Hi again, @rehevkor5! 👋 Was this intended for any use case beyond the one we just "fixed" with Glue crawlers? I would imagine most, if not all, AWS service calls that accept a IAM role name also accept a IAM role ARN in some fashion for the path problem.

While this is a fairly simple addition, I think we should try to not introduce additional code if it does not have strong use cases. If there are others, we would love to know. Thanks!

@bflad bflad added the waiting-response Maintainers are waiting on response from community or contributor. label Oct 30, 2018
@rehevkor5
Copy link
Contributor Author

@bflad My main concern was the issue with Glue Crawlers. I don't know whether there may be other places in the AWS API which work the same way or not. I assume it's possible to use the built-in functions of the config language to calculate this value manually, so now that Crawler Role ARN works properly & the documentation has been updated I think it's ok. I understand the motivation for omitting something that might not get a lot of use. Feel free to close, thanks for your attention.

@bflad
Copy link
Contributor

bflad commented Oct 30, 2018

If people are actually looking for this, we can certainly reopen and get this merged. Thanks for your understanding!

@bflad bflad closed this Oct 30, 2018
@ghost
Copy link

ghost commented Apr 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 2, 2020
@breathingdust breathingdust removed the waiting-response Maintainers are waiting on response from community or contributor. label Sep 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Introduces or discusses updates to documentation. enhancement Requests to existing resources that expand the functionality or scope. service/iam Issues and PRs that pertain to the iam service. size/S Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants