error.sh

± |master U:7 ✗| → terragrunt force-unlock db180055-ea34-ff85-f13d-2ec17b7a37af --terragrunt-source /Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-modules-acme/lambda/s3-image-processing
[terragrunt] [/Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-live-acme/main/us-east-1/prod/lambda/s3-image-processing] 2018/03/23 18:39:28 Running command: terraform --version
[terragrunt] 2018/03/23 18:39:29 Reading Terragrunt config file at /Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-live-acme/main/us-east-1/prod/lambda/s3-image-processing/terraform.tfvars
[terragrunt] 2018/03/23 18:39:29 WARNING: no double-slash (//) found in source URL /Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-modules-acme/lambda/s3-image-processing. Relative paths in downloaded Terraform code may not work.
[terragrunt] 2018/03/23 18:39:29 The --terragrunt-source-update flag is set, so deleting the temporary folder /Users/toni/.terragrunt/mIL2F0zQPCfKCN61doUEA8E6sf0/PvQdLQPbpvizuI4wEtEwh4ZDAhA before downloading source.
[terragrunt] 2018/03/23 18:39:29 Downloading Terraform configurations from file:///Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-modules-acme/lambda/s3-image-processing into /Users/toni/.terragrunt/mIL2F0zQPCfKCN61doUEA8E6sf0/PvQdLQPbpvizuI4wEtEwh4ZDAhA using terraform init
[terragrunt] [/Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-live-acme/main/us-east-1/prod/lambda/s3-image-processing] 2018/03/23 18:39:29 Initializing remote state for the s3 backend
[terragrunt] [/Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-live-acme/main/us-east-1/prod/lambda/s3-image-processing] 2018/03/23 18:39:31 Running command: terraform init -backend-config=region=us-east-1 -backend-config=dynamodb_table=terraform-locks -backend-config=encrypt=true -backend-config=bucket=acme-main-terraform-state -backend-config=key=us-east-1/prod/lambda/s3-image-processing/terraform.tfstate -from-module=file:///Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-modules-acme/lambda/s3-image-processing /Users/toni/.terragrunt/mIL2F0zQPCfKCN61doUEA8E6sf0/PvQdLQPbpvizuI4wEtEwh4ZDAhA
Copying configuration from "file:///Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-modules-acme/lambda/s3-image-processing"...
Initializing modules...
- module.lambda_s3
  Getting source "git::git@github.com:gruntwork-io/package-lambda.git//modules/lambda?ref=v0.2.1"

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Checking for available provider plugins on https://releases.hashicorp.com...
- Downloading plugin for provider "aws" (1.11.0)...
- Downloading plugin for provider "archive" (1.0.3)...
- Downloading plugin for provider "template" (1.0.0)...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

* provider.archive: version = "~> 1.0"
* provider.aws: version = "~> 1.11"
* provider.template: version = "~> 1.0"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
[terragrunt] 2018/03/23 18:39:45 Copying files from /Users/toni/Workspace/gruntwork/src/github.com/gruntwork-io/acme/infrastructure-live-acme/main/us-east-1/prod/lambda/s3-image-processing into /Users/toni/.terragrunt/mIL2F0zQPCfKCN61doUEA8E6sf0/PvQdLQPbpvizuI4wEtEwh4ZDAhA
[terragrunt] 2018/03/23 18:39:45 Setting working directory to /Users/toni/.terragrunt/mIL2F0zQPCfKCN61doUEA8E6sf0/PvQdLQPbpvizuI4wEtEwh4ZDAhA
[terragrunt] 2018/03/23 18:39:45 Backend s3 has not changed.
[terragrunt] 2018/03/23 18:39:46 Running command: terraform force-unlock db180055-ea34-ff85-f13d-2ec17b7a37af
Do you really want to force-unlock?
  Terraform will remove the lock on the remote state.
  This will allow local Terraform commands to modify this state, even though it
  may be still be in use. Only 'yes' will be accepted to confirm.

  Enter a value: yes

Failed to unlock state: failed to retrieve lock info: unexpected end of JSON input
[terragrunt] 2018/03/23 18:40:00 exit status 1