Fixes issues during apply all

* Jira lifecycle policy
* portal lambda data sync, missing variable

To overwrite existing tag v1.23.23

base/customer_portal_lambda/main.tf

@@ -116,6 +116,7 @@ resource "aws_lambda_function" "portal_data_sync" {
 			"NO_PROXY"               = "${var.dns_info["legacy_private"]["zone"]},${var.dns_info["private"]["zone"]}"
 			"VAULT_HOST"             = "vault.${var.dns_info["private"]["zone"]}"
 			"VAULT_PATH"             = "portal/data/lambda_sync_env"
+			"VERIFY_PORTAL_SSL"      = "0"
 		}
 	}
   tags = merge(var.standard_tags, var.tags)

base/jira/instance_jira/main.tf

@@ -34,8 +34,8 @@ resource "aws_instance" "jira-server-instance" {
   # We need to ignore ebs_block_device changes, because if the AMI changes, so does the snapshot_id.
   # If they add a feature to block more specific changes (eg `ebs_block_devices[*].snapshot_id`), then
   # that could be removed.
-  #lifecycle { ignore_changes = [ ami, key_name, user_data, ebs_block_device ] }
-  lifecycle { ignore_changes = [ ami, key_name, user_data ] }
+  lifecycle { ignore_changes = [ ami, key_name, user_data, ebs_block_device ] }
+  #lifecycle { ignore_changes = [ ami, key_name, user_data ] }
 
   # These device definitions are optional, but added for clarity.
   root_block_device {