terragrunt: Terraform fails when using remote_state.disable_init

I’m using disable_init to prevent terragrunt from accessing remote state bucket on its own (reason explained below). However, this also disables initializing the backend by terraform: it passes -backend=false to terraform init. As a result, the backend is not initialized and all terragrunt commands result in errors:

$ terragrunt plan
...
[terragrunt] [/tf] 2020/11/11 21:14:49 Running command: terraform init -backend=false
...
Terraform has been successfully initialized!
...
[terragrunt] 2020/11/11 21:14:56 Running command: terraform plan
Backend reinitialization required. Please run "terraform init".
Reason: Initial configuration of the requested backend "gcs"
...
Error: Initialization required. Please see the error message above

I think a better behavior would be have remote_state.disable_init prevent terragrunt itself from creating the state file in the remote bucket (or accessing the remote bucket bucket in any way), but not prevent terraform itself from initializing the state backend.

The reason this is needed in my case is that I’m using impersonate_service_account option in terraform 0.14-rc1, and terragrunt doesn’t understand it yet, so it fails whenever it tries to access the remote bucket. I hoped I could solve it by using emote_state.disable_init, but I run into this problem.