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

Error : Unsupported blocktype with new warm_pool feature #1332

Closed
JordyWTC opened this issue May 4, 2021 · 2 comments · Fixed by #1340
Closed

Error : Unsupported blocktype with new warm_pool feature #1332

JordyWTC opened this issue May 4, 2021 · 2 comments · Fixed by #1340

Comments

@JordyWTC
Copy link

JordyWTC commented May 4, 2021

Description

Hi when planning/applying the master branch of the terraform eks module an unsupporter block type error is being thrown :

│ Error: Unsupported block type
│ 
│   on .terraform/modules/eks/workers.tf line 115, in resource "aws_autoscaling_group" "workers":
│  115:   dynamic "warm_pool" {
│ 
│ Blocks of type "warm_pool" are not expected here.
╵
╷
│ Error: Unsupported block type
│ 
│   on .terraform/modules/eks/workers_launch_template.tf line 192, in resource "aws_autoscaling_group" "workers_launch_template":
│  192:   dynamic "warm_pool" {
│ 
│ Blocks of type "warm_pool" are not expected here.
``

Versions

  • Terraform: V 15.0
  • Provider(s): V 15.0

Reproduction

Steps to reproduce the behavior:
Perform a terraform plan / apply

Additional context

When i download the eks module myself and remove the warm_pool blocks out of the code, and call the module directly on local, it works correctly.

Im not creating any workers in my setup, as its a fargate setup. The code :

module "eks" {
  source                        = "git::https://github.com/terraform-aws-modules/terraform-aws-eks.git?ref=master"
  cluster_name             = var.name
  cluster_version          = var.cluster_version
  subnets                      = var.subnets
  vpc_id                        = var.vpc_id
  manage_worker_iam_resources   = false
  config_output_path                        = var.config_output_path
  write_kubeconfig                            = var.write_kubeconfig
  manage_aws_auth                         = var.manage_aws_auth
  map_users                                      = var.map_users
  map_roles                                       = var.map_roles
  manage_cluster_iam_resources     = var.manage_cluster_iam_resources
  cluster_iam_role_name                   = var.cluster_iam_role_name
  cluster_enabled_log_types              = var.cluster_enabled_log_types
  cluster_log_retention_in_days         = var.cluster_log_retention_in_days
  tags                                                  = var.tags
}
@rogersd
Copy link

rogersd commented May 5, 2021

Same thing here. See the comments on #1310 for more info.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants