EKS token as data source #37
Merged
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
autero1
approved these changes
Apr 8, 2019
robmorgan
approved these changes
Apr 8, 2019
|
Merging and releasing |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This introduces a new parameter to the
eks tokencommand that makes the command suitable for use as a terraform external data source. Specifically, this works around the limitation where the data source expects outputs to be in a flat map, encoded as JSON. The token output is in JSON, but the actual token data is nested in another map. Since we only need the actual token output and not the metadata in this mode of use, this command simply extracts out the token and puts it in a flat map of one attributetoken_data.