-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
RDD: Create Readme to describe how terragrunt will work #1
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
Conversation
This file contains hidden or 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
Closing this PR since it has been superseded by #2. |
brikis98
pushed a commit
that referenced
this pull request
Oct 6, 2018
Implement configuration init.
yorinasub17
pushed a commit
that referenced
this pull request
Jan 12, 2021
tests: add test coverage for RemoteStateConfigToTerraformCode #1165
denis256
pushed a commit
that referenced
this pull request
Nov 4, 2022
test: add test for params layer has file
denis256
added a commit
that referenced
this pull request
Jun 11, 2024
Found that in internal tests, only with WebIdentityToken, Terragrunt fails with: ``` time=2024-06-05T18:11:01Z level=error msg=Error finding AWS credentials (did you set the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables?): NoCredentialProviders: no valid providers in chain. Deprecated. For verbose messaging see aws.Config.CredentialsChainVerboseErrors time=2024-06-05T[18](https://github.com/gruntwork-test/testing-terragrunt-with-web-identity/actions/runs/9389092410/job/25855946545#step:6:19):11:01Z level=error msg=Unable to determine underlying exit code, so Terragrunt will exit with error code 1 ``` Fixed by updating AssumeIamRole
denis256
added a commit
that referenced
this pull request
Jun 13, 2024
* Add support for AssumeRoleWithWebIdentity Add support for STS [AssumeRoleWithWebIdentity](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html). Includes new config option `iam_web_identity_token` which takes either a WebIdentity token (designed to be passed in with `get_env()`), or a path to a file containing a WebIdentity token. * replace ioutil.ReadFile with os.ReadFile * fix flag name per new naming convention * remove unnecessary else clause * Add integration tests * Support passing through IAM role options through deleteS3Bucket * fix bug in TestTerragruntAssumeRoleWebIdentityEnv * Update and improve documentation * Fixed web credentials fetching (#1) Found that in internal tests, only with WebIdentityToken, Terragrunt fails with: ``` time=2024-06-05T18:11:01Z level=error msg=Error finding AWS credentials (did you set the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables?): NoCredentialProviders: no valid providers in chain. Deprecated. For verbose messaging see aws.Config.CredentialsChainVerboseErrors time=2024-06-05T[18](https://github.com/gruntwork-test/testing-terragrunt-with-web-identity/actions/runs/9389092410/job/25855946545#step:6:19):11:01Z level=error msg=Unable to determine underlying exit code, so Terragrunt will exit with error code 1 ``` Fixed by updating AssumeIamRole * Do not log the WebIdentity token * fix docs syntax issue * Updates from review feedback * fix comment --------- Co-authored-by: Matt Wilder <[email protected]> Co-authored-by: Denis O <[email protected]>
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 PR solely contains a README that describes how Terragrunt v0.0.1 can work. Submitting it now for early feedback before I dive into the implementation details.
The goal was to find the cheapest, simplest option for improving collaboration & locking in Terraform. To accomplish that, I’m offering two ways of locking that leverage tools you (probably) already have access to and are free or very inexpensive: Git and DynamoDB.