title: Switch terraform 0.12.6 to 0.13.0 gives me provider["registry.terraform.io/-/null"] is required, but it has been removed
body: <p><strong>I manage state in remote terraform-cloud</strong></p>
  <p>I have downloaded and installed the latest terraform 0.13 CLI</p>
  <p>Then I removed the <strong>.terraform</strong>.</p>
  <p>Then I ran <code>terraform init</code> and got no error</p>
  <p>then I did</p>
  <pre><code>➜ terraform apply -var-file env.auto.tfvars
  
  Error: Provider configuration not present
  
  To work with
  module.kubernetes.module.eks-cluster.data.null_data_source.node_groups[0] its
  original provider configuration at provider[&quot;registry.terraform.io/-/null&quot;] 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.kubernetes.module.eks-cluster.data.null_data_source.node_groups[0],
  after which you can remove the provider configuration again.
  
  Releasing state lock. This may take a few moments...
  </code></pre>
  <p>This is the content of the module/kubernetes/main.tf</p>
  <pre><code>###################################################################################
  # EKS CLUSTER                                                                     #
  #                                                                                 #
  # This module contains configuration for EKS cluster running various applications #
  ###################################################################################
  
  module &quot;eks_label&quot; {
    source      = &quot;git::https://github.com/cloudposse/terraform-null-label.git?ref=master&quot;
    namespace   = var.project
    environment = var.environment
    attributes  = [var.component]
    name        = &quot;eks&quot;
  }
  
  
  #
  # Local computed variables
  #
  locals {
    names = {
      secretmanage_policy = &quot;secretmanager-${var.environment}-policy&quot;
    }
  }
  
  data &quot;aws_eks_cluster&quot; &quot;cluster&quot; {
    name = module.eks-cluster.cluster_id
  }
  
  data &quot;aws_eks_cluster_auth&quot; &quot;cluster&quot; {
    name = module.eks-cluster.cluster_id
  }
  
  provider &quot;kubernetes&quot; {
    host                   = data.aws_eks_cluster.cluster.endpoint
    cluster_ca_certificate = base64decode(data.aws_eks_cluster.cluster.certificate_authority.0.data)
    token                  = data.aws_eks_cluster_auth.cluster.token
    load_config_file       = false
    version                = &quot;~&gt; 1.9&quot;
  }
  
  module &quot;eks-cluster&quot; {
    source          = &quot;terraform-aws-modules/eks/aws&quot;
    cluster_name    = module.eks_label.id
    cluster_version = var.cluster_version
    subnets         = var.subnets
    vpc_id          = var.vpc_id
  
    worker_groups = [
      {
        instance_type = var.cluster_node_type
        asg_max_size  = var.cluster_node_count
      }
    ]
  
    tags = var.tags
  }
  
  # Grant secretmanager access to all pods inside kubernetes cluster
  # TODO:
  # Adjust implementation so that the policy is template based and we only allow
  # kubernetes access to a single key based on the environment.
  # we should export key from modules/secrets and then grant only specific ARN access
  # so that only production cluster is able to read production secrets but not dev or staging
  # https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_identity-based-policies.html#permissions_grant-get-secret-value-to-one-secret
  resource &quot;aws_iam_policy&quot; &quot;secretmanager-policy&quot; {
    name        = local.names.secretmanage_policy
    description = &quot;allow to read secretmanager secrets ${var.environment}&quot;
    policy      = file(&quot;modules/kubernetes/policies/secretmanager.json&quot;)
  }
  
  #
  # Attache the policy to k8s worker role
  #
  resource &quot;aws_iam_role_policy_attachment&quot; &quot;attach&quot; {
    role       = module.eks-cluster.worker_iam_role_name
    policy_arn = aws_iam_policy.secretmanager-policy.arn
  }
  
  #
  # Attache the S3 Policy to Workers
  # So we can use aws commands inside pods easily if/when needed
  #
  resource &quot;aws_iam_role_policy_attachment&quot; &quot;attach-s3&quot; {
    role       = module.eks-cluster.worker_iam_role_name
    policy_arn = &quot;arn:aws:iam::aws:policy/AmazonS3FullAccess&quot;
  }
  </code></pre>