Skip to content

v0.13.1
Compare
Choose a tag to compare
@cloudpossebot cloudpossebot released this 13 Feb 09:40
0.13.1
fa04893
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

🚀 Enhancements

Add optional profile for accepter and requester @dtw45 (#38)

what

  • Allow user to pass in optional profile to be used when assuming the specified role.

why

  • As stated in the issue, if you normally configure profile in your aws provider block, plan will fail with the following message. This is because the default credentials don't have permission to assume the specified role.
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.


Error: error configuring Terraform AWS Provider: IAM Role (arn:aws:iam::XXXX:role/vpc-peering-role) cannot be assumed.

There are a number of possible causes of this - the most common are:
  * The credentials used in order to assume the role are invalid
  * The credentials do not have appropriate permission to assume the role
  * The role ARN is not valid

Error: NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

Also, there was a question of whether or not passing in an empty string would be okay for the AWS provider and it seems to work fine.

references

closes #7

Assets 2
Loading