feat: Add role unique_id output in iam-assumable-role module #143
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
carnei-ro
force-pushed
the
feat-assumable-role/output-role-unique-id
branch
from
4717586
to
133a9f5
Compare
carnei-ro
force-pushed
the
feat-assumable-role/output-role-unique-id
branch
from
133a9f5
to
cd9b076
Compare
|
LGTM @antonbabenko |
DrFaust92
approved these changes
Apr 7, 2021
antonbabenko
changed the title
|
v3.14.0 has been just released. |
|
Thanks guys! |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds a new output (
iam role unique-id) to moduleiam-assumable-roleMotivation and Context
We are using HashiCorp Vault version 1.2 and at this version, the only metadata we have to craft policies is the IAM Role Unique ID.
Breaking Changes
None
How Has This Been Tested?
examples/*projects