Terragrunt: Terragrunt Console Garbles STDIN/STDOUT Streams

Created on 4 Jun 2019  路  3Comments  路  Source: gruntwork-io/terragrunt

I experience a strange behavior with terragrunt console command. When I try to run the next command:

$ terragrunt console --terragrunt-source ...
...
[terragrunt] 2019/06/04 13:35:06 Running command: terraform console
Acquiring state lock. This may take a few moments...

<Ctrl + C>

Releasing state lock. This may take a few moments...

it looks like terragrunt hangs on acquiring state lock forever. However, if I change directory to terragrunt cache directory an try to run console manually through terraform CLI everything works as expected:

$ cd .terragrunt-cache/rXnIXItbUZO3QgycMk-_hiaL6ek/ZzjeLbJj6m48XPN-IEhSqTgSFCE
$ terraform console
Acquiring state lock. This may take a few moments...
> aws_route53_zone.this.zone_id
FAKE5JTM3YS01O
> exit
Releasing state lock. This may take a few moments...

All other terragrunt commands work as expected.

Later I found terragrunt console actually hides the console prompt and typed characters, but outputs results:

[terragrunt] 2019/06/04 13:35:06 Running command: terraform console
Acquiring state lock. This may take a few moments...

<hit Enter>
parse error at 1:3: expected expression but found ">"

<type 1>
1

<type aws_route53_zone.this.zone_id>
FAKE5JTM3YS01O

Seems like terragrunt garbles STDIN/STDOUT streams.

bug help wanted

Most helpful comment

All 3 comments

Confirming this, observed the same behavior

@yorinasub17 You rock! Thank you!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dingobar picture dingobar  路  3Comments

geekifier picture geekifier  路  3Comments

shaharmor picture shaharmor  路  3Comments

GauntletWizard picture GauntletWizard  路  3Comments

antonbabenko picture antonbabenko  路  3Comments