Terraform fails to init itself if cli_pager= has set no pager in .aws/config

[dimisjim]

Basically explained here: hashicorp/terraform-provider-aws#14450

[KaibaLopez]

Hi @dimisjim ,
This problem was addressed on this PR , so as of version 1.35 of the Go SDK you shouldn't be seeing this problem.
It might just be an issue of terraform not having updated its dependencies.

[dimisjim]

@KaibaLopez I am using terraform-provider-aws v3.22 which from here it seems it's using 1.36.x of the go sdk, but I am still getting this:

Error: error configuring S3 Backend: Error creating AWS session: SharedConfigLoadError: failed to load config file, /home/jim/.aws/config
caused by: INIParseError: invalid state with ASTKind { {4 NONE 0 [61]} true [{expr {1 STRING 0 [99 108 105 95 112 97 103 101 114]} true []}]} and TokenType none

issue also persists with latest terraform-provider-aws v3.25

[KaibaLopez]

@dimisjim ,
Can you show me your config file? (remove private info if there's any)
I just want to make sure I am trying the correct things to reproduce the error.

[dimisjim]

@KaibaLopez sure here you go:

[default]
cli_pager=

[KaibaLopez]

right, so I tried that and it works just fine with the SDK (assuming of course you have a [default] profile in your credentials on the .aws/credentials file).
Is that your full config file?

[dimisjim]

@KaibaLopez

Apparently this issue manifests only when there is no newline at the end of the config file.

So this does not work:

[default]
cli_pager=

but this does work fine:

[default]
cli_pager=

[KaibaLopez]

ahhh that would actually make sense with how I tested... I think it's only if

[default]
cli_pager=

is the last line that causes the fail, the sdk may be looking for a end of line indicator for it to know that cli_pager is empty, in my test I had other profiles after the one I tested so cli_pager= was not the last line.
But yea will take a look at that thanks!

[thezephyrus]

I faced the same issue while executing terraform commands.
My aws-config file had credentials with some profiles set for using AWS CLI.
I commented all the lines in the credentials file and was able to run the terraform commands.

[github-actions]

We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.

[dimisjim]

bump

[Anups155]

I faced the same issue while executing terraform commands. My aws-config file had credentials with some profiles set for using AWS CLI. I commented all the lines in the credentials file and was able to run the terraform commands.

[Anups155]

Thanks .. it worked!

[RanVaknin]

This is an old issue, not clear if this is still a problem. If it is please open a new issue on our v2 repo

Thanks,
Ran~

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.