Hii senpai, pwease accept my commit

[lamtnguyen989]

No description provided.

[github-actions]

Terraform plan in azure/terraform/stacks/acm-general in the prod workspace
With var files: azure/terraform/stacks/acm-general/configuration/prod.tfvars

Changes to Outputs.

Changes to Outputs:
!~  azurerm_dns_zone_acm_uic = {
        id                        = "/subscriptions/2f98793b-7e2f-4f03-ac5b-7b2ec934dcd7/resourceGroups/acm-general/providers/Microsoft.Network/dnsZones/acmuic.org"
        name                      = "acmuic.org"
!~      number_of_record_sets     = 68 -> 70
        tags                      = {}
#        (4 unchanged attributes hidden)
    }

You can apply this plan to save these new output values to the Terraform
state, without changing any real infrastructure.

❌ Plan not applied in Terraform Apply on Azure #57 (Plan has changed)

[github-actions]

Terraform plan in azure/terraform/stacks/sysadmin-demo in the prod workspace
With var files: azure/terraform/stacks/sysadmin-demo/configuration/prod.tfvars

Plan: 1 to add, 0 to change, 0 to destroy.

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+   create

Terraform will perform the following actions:

  # azurerm_dns_aaaa_record.overlord-max-nguyen will be created
+   resource "azurerm_dns_aaaa_record" "overlord-max-nguyen" {
+       fqdn                = (known after apply)
+       id                  = (known after apply)
+       name                = "overlord-max-nguyen"
+       records             = [
+           "fdc5:2d46:cdc1:b358::1",
        ]
+       resource_group_name = "acm-general"
+       ttl                 = 30
+       zone_name           = "acmuic.org"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

✅ Plan applied in Terraform Apply on Azure #57