fix: Ability to override existing cluster addons

Added the ability to override existing cluster addons via an optional flag

Signed-off-by: Deepak Devadathan <[email protected]>

Author: ddevadat

examples/cluster-addons/vars-cluster-addons.auto.tfvars

@@ -4,6 +4,7 @@
 cluster_addons = {
   "CertManager" = {
     remove_addon_resources_on_delete = true
+    override_existing = true           # Default is false if not specified
     # The list of supported configurations for the cluster addons is here: https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengconfiguringclusteraddons-configurationarguments.htm#contengconfiguringclusteraddons-configurationarguments_CertificateManager
     configurations = [
       {

modules/cluster-addons/addons.tf

@@ -35,8 +35,8 @@ resource "oci_containerengine_addon" "primary_addon" {
       value = tostring(lookup(config.value, "value"))
     }
   }
-
-  version = lookup(each.value, "version", null)
+  override_existing = lookup(each.value, "override_existing", false)
+  version           = lookup(each.value, "version", null)
 
   lifecycle {
 
@@ -67,8 +67,8 @@ resource "oci_containerengine_addon" "secondary_addon" {
       value = tostring(lookup(config.value, "value"))
     }
   }
-
-  version = lookup(each.value, "version", null)
+  override_existing = lookup(each.value, "override_existing", false)
+  version           = lookup(each.value, "version", null)
 
   lifecycle {