fix: update comment in code around apikey reset workaround (#64)

Author: ocofaigh

main.tf

@@ -176,8 +176,7 @@ resource "ibm_container_vpc_cluster" "autoscaling_cluster" {
 # run the ibmcloud ks api-key reset command to create one. The script will then pause for some time to allow any IAM
 # Cloudant replication to occur. By doing this, it means the cluster provisioning process will not attempt to create a
 # new key, and simply use the key created by this script. So hence should not face 404s anymore.
-# The script should be replaced by an ibm provider resource when support is added. That enhancement is being tracked in
-# https://github.com/IBM-Cloud/terraform-provider-ibm/issues/4292
+# The IKS team are tracking internally https://github.ibm.com/alchemy-containers/armada-ironsides/issues/5023
 
 resource "null_resource" "reset_api_key" {
   provisioner "local-exec" {

module-metadata.json

@@ -443,7 +443,7 @@
       },
       "pos": {
         "filename": "main.tf",
-        "line": 238
+        "line": 237
       }
     },
     "ibm_container_vpc_worker_pool.pool": {
@@ -459,7 +459,7 @@
       },
       "pos": {
         "filename": "main.tf",
-        "line": 206
+        "line": 205
       }
     },
     "ibm_resource_instance.cos_instance": {
@@ -487,7 +487,7 @@
       },
       "pos": {
         "filename": "main.tf",
-        "line": 290
+        "line": 289
       }
     },
     "null_resource.reset_api_key": {
@@ -499,7 +499,7 @@
       },
       "pos": {
         "filename": "main.tf",
-        "line": 182
+        "line": 181
       }
     }
   },
@@ -516,7 +516,7 @@
       },
       "pos": {
         "filename": "main.tf",
-        "line": 196
+        "line": 195
       }
     },
     "data.ibm_container_cluster_versions.cluster_versions": {