powellquiring

The second apply was successful at deleting and creating a new cluster. Everything went well: ``` module.vpc_ocp_cluster.ibm_container_vpc_cluster.cluster: Still creating... [1h30m41s elapsed] module.vpc_ocp_cluster.ibm_container_vpc_cluster.cluster: Creation complete after 1h30m43s [id=c81t1ned0a8lib39bvt0] module.configure_cluster_logdna.ibm_ob_logging.logging: Creating... module.configure_cluster_logdna.ibm_ob_logging.logging:...

This should be a "force new" attribute of the subnet.

I really want this to work: ``` resource "ibm_is_subnet" "subnets" { name = var.basename vpc = ibm_is_vpc.vpc.id zone = local.zones[0] total_ipv4_address_count = 256 resource_group = data.ibm_resource_group.group.id # Step 1: terraform...

Expected: A terraform configuration is an unambiguous specification of the desired state. Actual: The subnet.routing_table value is going to be different depending on the configuration history. My staging and production...

I was able to reproduce using the steps provided, they are repeated below. Did you try these steps? ``` cd /tmp git clone https://github.com/powellquiring/tfbugs cd tfbugs/bug-vpc-endpoint-gateway-security-group terraform init terraform apply...

Maybe same as https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_instance_volume_attachment Allowed values are : [general-purpose, 5iops-tier, 10iops-tier, custom].

- [ ] I tried the example provided in the docs and it did not work: ``` volume_attachments { delete_volume_on_instance_delete = true name = "${var.name}-template-volume-attachment" volume_prototype { iops = 3000...

Handle docs to profile same was as api spec: https://github.ibm.com/riaas/api-spec/issues/4081

Happened again, I think the instance the floating ip was connected to did not get created on the previous run.

I'm working around this problem, maybe that is contributing, let me look a little harder: https://github.com/IBM-Cloud/terraform-provider-ibm/issues/3740