Skip to content
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

getting version issue #14183

Open
shikharkhanna opened this issue Jul 15, 2020 · 2 comments
Open

getting version issue #14183

shikharkhanna opened this issue Jul 15, 2020 · 2 comments
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. stale Old or inactive issues managed by automation, if no further action taken these will get closed.

Comments

@shikharkhanna
Copy link

Terraform CLI and Terraform AWS Provider Version

TERRAFORM_VERSION=0.11.7
TERRAGRUNT_VERSION=0.14.7

Affected Resource(s)

  • aws_XXXXX

Terraform Configuration Files

Main.tf

provider "aws" {
access_key = "${var.aws_access_key}"
secret_key = "${var.aws_secret_key}"
region = "eu-west-1"
}

terraform {

The configuration for this backend will be filled in by Terragrunt

backend "s3" {
bucket = "content-peer-terraform-state"
key = "content-test-terraform.tfstate"
region = "eu-west-1"
dynamodb_table = "my-lock-table"
encrypt = true
}
}

module "peer_connection" {
source = "../common/peer-connection"
env = "${var.env}"
version = "$Latest"
}

Debug Output

Created a file on 0.46.0
[terragrunt] [/tmp/build/1cf6b43f/git-repo/peer-connection/infrastructure/environments/test] 2020/07/15 14:52:45 Running command: terraform --version
[terragrunt] 2020/07/15 14:52:45 Reading Terragrunt config file at /tmp/build/1cf6b43f/git-repo/peer-connection/infrastructure/environments/test/.terragrunt
[terragrunt] 2020/07/15 14:52:45 DEPRECATION WARNING: Found deprecated config file format /tmp/build/1cf6b43f/git-repo/peer-connection/infrastructure/environments/test/.terragrunt. This old config format will not be supported in the future. Please move your config files into a terraform.tfvars file.
[terragrunt] [/tmp/build/1cf6b43f/git-repo/peer-connection/infrastructure/environments/test] 2020/07/15 14:52:45 Initializing remote state for the s3 backend
[terragrunt] [/tmp/build/1cf6b43f/git-repo/peer-connection/infrastructure/environments/test] 2020/07/15 14:52:45 Running command: terraform init -backend-config=key=content-test-terraform.tfstate -backend-config=region=eu-west-1 -backend-config=dynamodb_table=my-lock-table -backend-config=encrypt=true -backend-config=bucket=content-peer-terraform-state
Initializing modules...

  • module.peer_connection
    Getting source "../common/peer-connection"

Initializing the backend...

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

Error: module "peer_connection": missing required argument "version"

[terragrunt] 2020/07/15 14:52:46 Hit multiple errors:
exit status 1

Expected Behavior

should successfully run terragrunt apply

Actual Behavior

terragrunt apply -var-file=./$INFRA_ENV/terraform.tfvars -auto-approve -input=false -lock=false --terragrunt-non-interactive

Steps to Reproduce

Trying to run terragrunt apply in concourse to create some resources in AWS using this pipeline snippet

run:
dir: git-repo/peer-connection
path: bash
args:
- -ec
- |
echo "Created a file on " $(cat ../../infra-version/version)
export TF_VAR_version=$(cat ../../infra-version/version)
cd infrastructure/environments/test
terragrunt apply -var-file=./$INFRA_ENV/terraform.tfvars -auto-approve -input=false -lock=false --terragrunt-non-interactive

References

  • #0000
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Jul 15, 2020
@shikharkhanna
Copy link
Author

Hi

Any updates on this please?

@breathingdust breathingdust added question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. and removed needs-triage Waiting for first response or review from a maintainer. labels Sep 21, 2021
Copy link

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. stale Old or inactive issues managed by automation, if no further action taken these will get closed.
Projects
None yet
Development

No branches or pull requests

2 participants