-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Terraformer Unable to use Profile assignment #1945
Comments
Confirming this behaviour. Setting profile to |
To hell it resolves auth issues. Modern type of auth is SSO, not IAM roles. Terraform itself works beautifully.
|
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Maintainers please advise if not kosher.. but this is still an issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, there were previous attempts to re-open the following issue. I can confirm the issue exists in current release
v0.8.24
When looking at the AWS configuration file we can see the following:
This configuration will not work no matter how you attempt to execute the command (even with ENV VAR's), but the underlying AWS commands/terraform commands will succeed.
You have to change the config to the following, and utilize the default profile:
Failed Command:
terraformer import aws --resources=vpc,subnet --profile "YOUR_ADMIN_PROFILE"
Successful command:
terraformer import aws --resources=vpc,subnet --profile ""
Example output:
This is related to the following: #940
The text was updated successfully, but these errors were encountered: