#terraform - September 2019

Join us for "Office Hours" every Wednesday 11:30AM (PST, GMT-7) via Zoom.

👉️ Register for Webinar

#office-hours (our channel)

Error: Provider configuration not present

To work with
module.cicd-web.aws_iam_policy_attachment.cloudformation_policy_attachment its
original provider configuration at module.cicd-web.provider.aws.nonprod is
required, but it has been removed. This occurs when a provider configuration
is removed while objects created by that provider still exist in the state.
Re-add the provider configuration to destroy
module.cicd-web.aws_iam_policy_attachment.cloudformation_policy_attachment,
after which you can remove the provider configuration again.

locals {
  users = ["user1", "user2"]
}

resource "aws_iam_user" "this" {
  for_each = toset(local.users)
  name     = "${each.value}"
}

resource "aws_iam_access_key" "this" {
  for_each = toset(local.users)

  user = # Reference above created users
}

    user = aws_iam_user.this[each.key].name

Join us for "Office Hours" every Wednesday 11:30AM (PST, GMT-7) via Zoom.

👉️ Register for Webinar

#office-hours (our channel)

  db_subnet_group_name = "${element(data.my_state.networking.database_subnets,1)}"

  on .terraform/modules/alb_magento2/main.tf line 33, in resource "aws_security_group_rule" "http_ingress":
  33:   cidr_blocks       = [var.http_ingress_cidr_blocks]

Error: error validating provider credentials: error calling sts:GetCallerIdentity: NoCredentialProviders: no valid providers in chain. Deprecated.

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  profile = "storesnonprod"
  alias   = "nonprod"
}

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  profile = "storesprod"
  alias   = "prod"
}

Error: Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
	status code: 409, request id: aaaa, host id: aaaa//bbbb+cxxx=

run:
	# Apply Backend module using local State file
	direnv allow
	bash toggle-s3.sh local
	terraform init && terraform apply
	# Switch to S3 State storage
	bash toggle-s3.sh s3
	terraform init && terraform apply

Error: Error in function call

  on .terraform/modules/terraform_state_backend/main.tf line 193, in data "template_file" "terraform_backend_config":
 193:       coalescelist(
 194:
 195:
 196:
    |----------------
    | aws_dynamodb_table.with_server_side_encryption is empty tuple
    | aws_dynamodb_table.without_server_side_encryption is empty tuple

Call to function "coalescelist" failed: no non-null arguments.

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  profile = "ambassadorsnonprod"
  alias   = "nonprod"
}

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  profile = "ambassadorsprod"
  alias   = "prod"
}

To work with
module.cicd-web.aws_iam_policy_attachment.cloudformation_policy_attachment its
original provider configuration at module.cicd-web.provider.aws.nonprod is
required, but it has been removed. This occurs when a provider configuration
is removed while objects created by that provider still exist in the state.
Re-add the provider configuration to destroy
module.cicd-web.aws_iam_policy_attachment.cloudformation_policy_attachment,
after which you can remove the provider configuration again.

module.datamart_secondary_cluster.aws_rds_cluster.default[0]: Creation complete after 9m10s [id=example-stage-pepe1secondary]
module.datamart_secondary_cluster.aws_rds_cluster_instance.default[1]: Creating...
module.datamart_secondary_cluster.aws_rds_cluster_instance.default[0]: Creating...
module.datamart_secondary_cluster.aws_rds_cluster_instance.default[0]: Still creating... [10s elapsed]
module.datamart_secondary_cluster.aws_rds_cluster_instance.default[1]: Still creating... [10s elapsed]
module.datamart_secondary_cluster.aws_rds_cluster_instance.default[1]: Still creating... [20s elapsed]
module.datamart_secondary_cluster.aws_rds_cluster_instance.default[0]: Still creating... [20s elapsed]

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  alias   = "nonprod"
}

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  alias   = "prod"
}

provider "aws" {
  version    = "~> 2.25.0"
  region     = var.aws_region
  profile    = "storesnonprod"
  alias      = "nonprod"
}

provider "aws" {
  version    = "~> 2.25.0"
  region     = var.aws_region
  profile    = "storesprod"
  alias      = "prod"
}

module "cicd-web" {
  source = "../../modules/cicd-web"

  providers = {
    aws.nonprod = "aws.nonprod"
    aws.prod    = "aws.prod"
  }
........

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  alias   = "nonprod"
}

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  alias   = "prod"
}

provider "aws" {
  region                  = "us-west-2"
  shared_credentials_file = "/Users/tf_user/.aws/creds"
  profile                 = "customprofile"
}

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  alias   = "nonprod"
}

provider "aws" {
  version = "~> 2.25.0"
  region  = var.aws_region
  alias   = "prod"
}

provider "aws" {
  version    = "~> 2.25.0"
  region     = var.aws_region
  profile    = "storesnonprod"
  alias      = "nonprod"
}

provider "aws" {
  version    = "~> 2.25.0"
  region     = var.aws_region
  profile    = "storesprod"
  alias      = "prod"
}

module "cicd-web" {
  source = "../../modules/somemodule"

  providers = {
    aws.nonprod = "aws.nonprod"
    aws.prod    = "aws.prod"
  }

Error: Provider configuration not present

To work with
module.somemodule.aws_iam_policy_attachment.codepipeline_policy_attachment its
original provider configuration at module.somemodule.provider.aws.nonprod is
required, but it has been removed. This occurs when a provider configuration
is removed while objects created by that provider still exist in the state.
Re-add the provider configuration to destroy
module.somemodule.aws_iam_policy_attachment.codepipeline_policy_attachment,
after which you can remove the provider configuration again.

resource "aws_ecs_task_definition" "jenkins_simple_service" {

//  volume {
//    name      = "docker-socket"
//    host_path = "/var/run/docker.sock"
//  }

  volume {
    name      = "jenkins-data"
    host_path = "/home/ec2-user/data"
  }
  family                = "jenkins-simple-service"
  container_definitions = file("task-definitions/jenkins-gig.json")
}

resource "aws_ecs_service" "jenkins_simple_service" {
  name            = "jenkins-gig"
  cluster         = data.terraform_remote_state.ecs.outputs.staging_id
  task_definition = aws_ecs_task_definition.jenkins_simple_service.arn
  desired_count   = 1
  iam_role        = data.terraform_remote_state.ecs.outputs.service_role_id

  load_balancer {
    elb_name       = data.terraform_remote_state.ecs.outputs.simple_service_elb_id
    container_name = "jenkins-gig"
    container_port = 8080
  }
}

[
  {
    "name": "jenkins-gig",
    "image": "my-image",
    "cpu": 0,
    "memory": 512,
    "essential": true,
    "portMappings": [
      {
        "containerPort": 8080,
        "hostPort": 8000
      }
    ],
    "environment" : [
      {
        "name" : "VIRTUAL_HOST",
        "value" : "<host>"
      },
      {
        "name": "VIRTUAL_PORT",
        "value": "8080"
      }
    ],
    "mountPoints": [
      {
        "sourceVolume": "jenkins-data",
        "containerPath": "/var/jenkins_home",
        "readOnly": false
      }
    ]
  },
  {
    "name": "nginx-proxy",
    "image": "jwilder/nginx-proxy",
    "cpu": 0,
    "memory": 512,
    "essential": true,
    "portMappings": [
      {
        "containerPort": 80,
        "hostPort": 80
      }
    ]
  }
]

Join us for "Office Hours" every Wednesday 11:30AM (PST, GMT-7) via Zoom.

👉️ Register for Webinar

#office-hours (our channel)

Error: Invalid count argument

  on .terraform/modules/eks_workers.autoscale_group/ec2-autoscale-group/main.tf line 120, in data "null_data_source" "tags_as_list_of_maps":
 120:   count = var.enabled ? length(keys(var.tags)) : 0

The "count" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the count depends on.

module "eks_cluster" {

  source     = "git::<https://github.com/instructure/terraform-aws-eks-cluster.git?ref=master>"
...
}

module "eks_workers" {
  source = "git::<https://github.com/instructure/terraform-aws-eks-workers.git?ref=inst-version>"
...

Error: Invalid count argument

  on .terraform/modules/eks_workers.autoscale_group/main.tf line 120, in data "null_data_source" "tags_as_list_of_maps":
 120:   count = var.enabled ? length(keys(var.tags)) : 0

The "count" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the count depends on.

module "eks_workers" {
  source = "git::<https://github.com/instructure/terraform-aws-eks-workers.git?ref=inst-version>"

  namespace     = var.namespace
  stage         = var.stage
  name          = var.name
  tags          = var.tags
...
}

# mine
  cluster_name                       = "${module.eks_cluster.eks_cluster_id}"

repos:
- repo: <git://github.com/antonbabenko/pre-commit-terraform>
  rev: v1.15.0
  hooks:
    - id: terraform_fmt
    - id: terraform_docs_replace

 pkg_resources.DistributionNotFound: The 'pre-commit-terraform' distribution was not found and is required by the application

module "vpc_staging" {
  source = "./vpc_staging"
}

module "security-group" {
  source  = "terraform-aws-modules/security-group/aws"
  version = "1.25.0"

  name = "sg"
  description = "Security group for n/w with needed ports open within VPC"
  vpc_id     = "${module.vpc_staging.vpc_id}"

}

module "subnets" {
  source              = "git::<https://github.com/cloudposse/terraform-aws-dynamic-subnets.git?ref=tags/0.12.0>"

locals {
  availability_zones = slice(data.aws_availability_zones.available.names, 0, 2)
}

Error: Run variables are currently not supported

The "remote" backend does not support setting run variables at this time.
Currently the only to way to pass variables to the remote backend is by
creating a '*.auto.tfvars' variables file. This file will automatically be
loaded by the "remote" backend when the workspace is configured to use
Terraform v0.10.0 or later.

Additionally you can also set variables on the workspace in the web UI:
<https://app.terraform.io/app/Boulevard/sched-dev-feature-branch-environments/variables>

    principals {
      type        = "AWS"
      identifiers = [replace("${aws_cloudfront_origin_access_identity.this.iam_arn}", " ", "_")]
    }

Error: Error putting S3 policy: MalformedPolicy: Invalid principal in policy

Join us for "Office Hours" every Wednesday 11:30AM (PST, GMT-7) via Zoom.

👉️ Register for Webinar

#office-hours (our channel)