azurerm_monitor_diagnostic_setting re-applies changes/updates every time running plan or apply... #10388

kon1180 · 2021-01-29T20:59:27Z

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

terraform {
  required_version = "~> 0.13.0"

  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~> 2.44.0" # "~> 2.33.0"
    }
  }
}

Affected Resource(s)

azurerm_monitor_diagnostic_setting when applying to Azure SQL DB and Synapse Pool

Expected Behaviour

After running Terraform apply, Terraform apply/plan again should say no changes

Actual Behaviour

After running Terraform plan/apply, will apply the same changes again and again.
Below is a pic of what I am seeing everytime I re-run Terraform plan, ie. it is applying those same changes every time, but terraform should only update what has changed net:

Steps to Reproduce

terraform plan

Code

The resource created and the azurerm_monitor_diagnostic_setting used to send resource logs out:
Azure SQL DB:

# Create Azure SQL DB
resource "azurerm_sql_database" "sqldb" {
  name                = "${var.org}-sqldb-dgtlbi-${var.environment}-001"
  resource_group_name = var.resource_group_name
  location            = var.location
  server_name         = azurerm_sql_server.sqlserver.name
  max_size_bytes      = 2147483648 # 2GB
  edition             = "Basic"

}

# Sending SQL DB Logs to Qradar eventhub
# Logging categories: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/resource-logs-categories#microsoftsqlserversdatabases
resource "azurerm_monitor_diagnostic_setting" "sqldb_log_qradar" {
  name                           = "${var.org}-sqldb-dgtlbi-${var.environment}-001-log-name"
  target_resource_id             = azurerm_sql_database.sqldb.id
  eventhub_name                  = local.qradar_eventhub_name
  eventhub_authorization_rule_id = local.qradar_eventhub_authorization_rule_id

  log {
    category = "Deadlocks"

    retention_policy {
      enabled = true
      days    = 0
    }
  }

  log {
    category = "Errors"

    retention_policy {
      enabled = true
      days    = 0
    }
  }

  log {
    category = "SQLSecurityAuditEvents"

    retention_policy {
      enabled = true
      days    = 0
    }
  }


  metric {
    category = "AllMetrics"
    enabled  = true

    retention_policy {
      days    = 0
      enabled = true
    }
  }
}

Azure Synapse Pool


# Create Azure Synapse Pool - no workspace
resource "azurerm_mssql_database" "syn" {
  name      = "${var.org}-syn-dgtlbi-${var.environment}-001"
  server_id = azurerm_sql_server.sqlserver.id
  sku_name  = "DW100c"

}

# Sending Synapse Pool Logs to Qradar eventhub
# Logging categories: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/resource-logs-categories#microsoftsqlserversdatabases
resource "azurerm_monitor_diagnostic_setting" "syn_log_qradar" {
  name                           = "${var.org}-syn-dgtlbi-${var.environment}-001-log-name"
  target_resource_id             = azurerm_mssql_database.syn.id
  eventhub_name                  = local.qradar_eventhub_name
  eventhub_authorization_rule_id = local.qradar_eventhub_authorization_rule_id

  log {
    category = "SQLSecurityAuditEvents"

    retention_policy {
      enabled = true
      days    = 0
    }
  }

  log {
    category = "SqlRequests"

    retention_policy {
      enabled = true
      days    = 0
    }
  }

  log {
    category = "ExecRequests"

    retention_policy {
      enabled = true
      days    = 0
    }
  }

  metric {
    category = "AllMetrics"
    enabled  = true

    retention_policy {
      days    = 0
      enabled = true
    }
  }
}

The text was updated successfully, but these errors were encountered:

flo-02-mu · 2021-12-29T10:19:35Z

I did a bit of an investigation: As soon as one diagnostic setting (regardless whether it is "log" or "monitor") is enabled for a target resource, the API returns all available diagnostic settings for that target resource with the default values (enabled: false and retention: 0):

az rest --method get --url https://management.azure.com/subscriptions/****/resourceGroups/test-for-github-10388/providers/Microsoft.KeyVault/vaults/test-for-github-10388/providers/Microsoft.Insights/diagnosticSettings/github-issue-10388?api-version=2021-05-01-preview

{
  "id": "/subscriptions/****/resourcegroups/test-for-github-10388/providers/microsoft.keyvault/vaults/test-for-github-10388/providers/microsoft.insights/diagnosticSettings/github-issue-10388",
  "identity": null,
  "kind": null,
  "location": null,
  "name": "github-issue-10388",
  "properties": {
    "eventHubAuthorizationRuleId": null,
    "eventHubName": null,
    "logAnalyticsDestinationType": null,
    "logs": [
      {
        "category": "AuditEvent",
        "categoryGroup": null,
        "enabled": false,
        "retentionPolicy": {
          "days": 0,
          "enabled": false
        }
      },
      {
        "category": "AzurePolicyEvaluationDetails",
        "categoryGroup": null,
        "enabled": false,
        "retentionPolicy": {
          "days": 0,
          "enabled": false
        }
      }
    ],
    "metrics": [
      {
        "category": "AllMetrics",
        "enabled": true,
        "retentionPolicy": {
          "days": 0,
          "enabled": false
        }
      }
    ],
    "serviceBusRuleId": null,
    "storageAccountId": null,
    "workspaceId": "/subscriptions/****/resourceGroups/oasis-tst-loganalytics/providers/Microsoft.OperationalInsights/workspaces/oasis-tst-analytics"
  },
  "resourceGroup": "test-for-github-10388",
  "tags": null,
  "type": "Microsoft.Insights/diagnosticSettings"
}

Terraform then interprets this existence as change from null to false and wants to change it back - which does not work.
A simple way of changing the behaviour would be to only check for enabled settings and treat "null" and "disabled" identical. E.g. by adding

if *v.Enabled{
	results = append(results, output)
}

at https://github.com/hashicorp/terraform-provider-azurerm/blob/main/internal/services/monitor/monitor_diagnostic_setting_resource.go#L480

This has some side-effects though when explicitly specifying "enabled: false" like it is done in the tests (e.g. https://github.com/hashicorp/terraform-provider-azurerm/blob/main/internal/services/monitor/monitor_diagnostic_setting_resource_test.go#L277)
The setup would mean to either specify "enabled = true" or to not specify the block at all... not sure if this is desired.

PPACI · 2022-02-07T09:15:56Z

I would like to see the proposed solution implemented.
Some Azure Policy and Microsoft Defender for cloud will automatically enables diagnostic log.
This operation will then change the state as explained above.

The ignore lifecycle doesn't work in this scenario.

For us, the workaround is to specify the automatic policy in the terraform code as if some audit-log were setup by terraform.
It works but we would like to keep some diagnostic log (specially the security ones) outside of terraform and we currently are unable to.

The proposed "explicitly specify enabled=true/false to manage" would be perfect for us.

I can propose a PR with the changes if that's OK for you.

SenorRagequit · 2022-02-23T17:45:53Z

Still happening.
As soon as you define anything, azure automatically sets everything else to 0 if not defined.
Terraform sees that 0 as a new change, since 0 isn't NULL.

biswarup1290dass · 2022-02-25T18:22:51Z

I am seeing similar problem for AKS Diagnostics where I split diff log category to two types of storage (few configured to store in Log Analytics and few in Storage Account).

Below is my TF file to create the azurerm_monitor_diagnostice_setting resources:

resource "azurerm_monitor_diagnostic_setting" "aks_audit" {
  lifecycle {
    ignore_changes = [target_resource_id]
  }
  name                       = ${local.diag_name}
  log_analytics_workspace_id = azurerm_log_analytics_workspace.workspace.id
  target_resource_id         = data.azurerm_kubernetes_cluster.aks.id

  log {
    category = "cloud-controller-manager"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }

  log {
    category = "cluster-autoscaler"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }

  log {
    category = "kube-apiserver"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }

  log {
    category = "kube-controller-manager"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }

  log {
    category = "kube-scheduler"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }

  log {
    category = "guard"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }

  metric {
    category = "AllMetrics"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }
}


resource "azurerm_monitor_diagnostic_setting" "aks_audit_sa" {
  lifecycle {
    ignore_changes = [target_resource_id]
  }
  name                       =  ${local.sa_diag_name}
  storage_account_id         = azurerm_storage_account.audit_sa.id
  target_resource_id         = data.azurerm_kubernetes_cluster.aks.id
  log {
    category = "kube-audit"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }

  log {
    category = "kube-audit-admin"
    enabled  = true

    retention_policy {
      days    = 90
      enabled = true
    }
  }
}

The plan shows something like

# azurerm_monitor_diagnostic_setting.aks_audit will be updated in-place
  ~ resource "azurerm_monitor_diagnostic_setting" "aks_audit" {
        id                 = <REDACTED>
        name               = <REDACTED>
        # (2 unchanged attributes hidden)

      - log {
          - category = "csi-azuredisk-controller" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "csi-azurefile-controller" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "csi-snapshot-controller" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "kube-audit" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "kube-audit-admin" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }

        # (7 unchanged blocks hidden)
    }

  # azurerm_monitor_diagnostic_setting.aks_audit_sa will be updated in-place
  ~ resource "azurerm_monitor_diagnostic_setting" "aks_audit_sa" {
        id                 = <REDACTED>
        name               = <REDACTED>
        # (2 unchanged attributes hidden)

      - log {
          - category = "cloud-controller-manager" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "cluster-autoscaler" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "csi-azuredisk-controller" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "csi-azurefile-controller" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "csi-snapshot-controller" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "guard" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "kube-apiserver" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "kube-controller-manager" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
      - log {
          - category = "kube-scheduler" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }

      - metric {
          - category = "AllMetrics" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }
        # (2 unchanged blocks hidden)
    }

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

This is the plan on every TF plan exec, w/o any variable changes. Had to add the lifecycle meta arg when this happened last time but the mentioned request handling on the Azure API end is forcing the provider to identify a change every time.

I had to explicitly specify all the categories(log as well as metric) that I don't need as below to make TF dodge the "undesired" changes.

ex:

log {
    category = "CATEGORY"
    enabled  = false
    retention_policy {
      days    = 0
      enabled = false
    }
  }

Till this issue remains open/unresolved, I need to keep adding whenever a new diagnostic log category is introduced by Azure and enforced.

murdibb · 2022-03-14T17:29:39Z

Hi all,

Below my workaround which resulted in no unneeded changes detected.
AzureRM provider version: 2.93.1
Terraform version: 0.13.7

a local list variable containing the categories I want to enable logs/metrics

locals {
  example_recovery_vault_diagnostic_categories_enabled = [
    "AzureSiteRecoveryJobs",
    "AzureSiteRecoveryRecoveryPoints"
  ]
}

data source to get ALL the available categories

data "azurerm_monitor_diagnostic_categories" "example" {
  resource_id = azurerm_recovery_services_vault.example.id
}

dynamic block that generates all the categories including the ones I need, and also the ones I want to disable with respective settings. Condition for "enable = true" is as you can see, if the category matches my list or not.

resource "azurerm_monitor_diagnostic_setting" "example" {
  name                           = azurerm_recovery_services_vault.example.name
  target_resource_id             = azurerm_recovery_services_vault.example.id
  log_analytics_workspace_id     = data.azurerm_log_analytics_workspace.example.id
  log_analytics_destination_type = "AzureDiagnostics"
  
  dynamic "log" {
    iterator = log_category
    for_each = data.azurerm_monitor_diagnostic_categories.example.logs

    content {
      enabled  = contains(local.example_recovery_vault_diagnostic_categories_enabled,log_category.value) ? true : false
      category = log_category.value
      retention_policy {
        days     = 0
        enabled  = contains(local.example_recovery_vault_diagnostic_categories_enabled,log_category.value) ? true : false
      }
    }
  }

  dynamic "metric" {
    iterator = metric_category
    for_each = data.azurerm_monitor_diagnostic_categories.example.metrics

    content {
      enabled  = contains(local.example_recovery_vault_diagnostic_categories_enabled,metric_category.value) ? true : false
      category = metric_category.value
      retention_policy {
        days     = 0
        enabled  = contains(local.example_recovery_vault_diagnostic_categories_enabled,metric_category.value) ? true : false
      }
    }
  }
}

or-shachar · 2022-03-16T16:29:55Z

@murdibb worked for us - thanks!

MageshSrinivasulu · 2022-03-31T13:35:25Z

It works for us as well. Tested it.

guidooliveira · 2022-08-08T23:26:54Z

Hi all,

Below my workaround which resulted in no unneeded changes detected. AzureRM provider version: 2.93.1 Terraform version: 0.13.7

a local list variable containing the categories I want to enable logs/metrics

locals {
  example_recovery_vault_diagnostic_categories_enabled = [
    "AzureSiteRecoveryJobs",
    "AzureSiteRecoveryRecoveryPoints"
  ]
}

data source to get ALL the available categories

data "azurerm_monitor_diagnostic_categories" "example" {
  resource_id = azurerm_recovery_services_vault.example.id
}

dynamic block that generates all the categories including the ones I need, and also the ones I want to disable with respective settings. Condition for "enable = true" is as you can see, if the category matches my list or not.

resource "azurerm_monitor_diagnostic_setting" "example" {
  name                           = azurerm_recovery_services_vault.example.name
  target_resource_id             = azurerm_recovery_services_vault.example.id
  log_analytics_workspace_id     = data.azurerm_log_analytics_workspace.example.id
  log_analytics_destination_type = "AzureDiagnostics"
  
  dynamic "log" {
    iterator = log_category
    for_each = data.azurerm_monitor_diagnostic_categories.example.logs

    content {
      enabled  = contains(local.example_recovery_vault_diagnostic_categories_enabled,log_category.value) ? true : false
      category = log_category.value
      retention_policy {
        days     = 0
        enabled  = contains(local.example_recovery_vault_diagnostic_categories_enabled,log_category.value) ? true : false
      }
    }
  }

  dynamic "metric" {
    iterator = metric_category
    for_each = data.azurerm_monitor_diagnostic_categories.example.metrics

    content {
      enabled  = contains(local.example_recovery_vault_diagnostic_categories_enabled,metric_category.value) ? true : false
      category = metric_category.value
      retention_policy {
        days     = 0
        enabled  = contains(local.example_recovery_vault_diagnostic_categories_enabled,metric_category.value) ? true : false
      }
    }
  }
}

Unfortunatelly, even this isn't working anymore for me, the data call doesn't seem to be called during plan, which still triggers changes.

kamilzzz · 2023-02-16T17:47:52Z

Version 3.39.0 of azurerm provider introduced new block enabled_log under azurerm_monitor_diagnostic_setting resource.

In my case, transitioning existing log blocks to enabled_log blocks fixed the issue and Terraform no longer tries to apply the same changes in every Terraform plan/apply runs.

mtrin · 2023-02-21T12:30:51Z

Version 3.39.1 with enabled_log still has the same issue for me

mukeshinit · 2023-05-15T19:06:26Z

Version 3.39.0 of azurerm provider introduced new block enabled_log under azurerm_monitor_diagnostic_setting resource. fixed the enabled_log block issue .

But same issue exists for the metric block and it tries to apply the same changes over and over every Terraform plan/apply runs.

shanilhirani · 2023-06-19T13:28:30Z

Would having an enabled_metrics improve the situation as some have reported that the new attribute (enabled_log) has resolved their terraform drift?

Stolz · 2023-10-20T07:20:04Z

For me it keeps happening even when using enabled_log. My workaround is to ignore the changes with a lifecycle > ignore_changes block

resource "azurerm_monitor_diagnostic_setting" "ds" {
  log_analytics_workspace_id = var.log_analytics_workspace_id
  name                       = var.diagnostic_setting_name
  target_resource_id         = var.target_resource_id

  dynamic "enabled_log" {
    for_each = var.logs_categories 

    content {
      category = enabled_log.value
    }
  }

  lifecycle {
    ignore_changes = [enabled_log, log, metric] # Workaround for BUG https://github.com/terraform-providers/terraform-provider-azurerm/issues/10388
  }
}

Kulesza · 2023-12-25T20:46:10Z

The same problem exists for the Synapse workspace.

The diagnostics have no metrics. But a category AllMetrics is created automatically.
Every run forces terraform to remove those.

- metric {
          - category = "AllMetrics" -> null
          - enabled  = false -> null

          - retention_policy {
              - days    = 0 -> null
              - enabled = false -> null
            }
        }

This comment has been minimized.

Sign in to view

This comment was marked as off-topic.

Sign in to view

katbyte added bug service/monitor labels Jun 23, 2021

This comment was marked as off-topic.

Sign in to view

red-hood mentioned this issue Nov 11, 2021

unexpected behavior for azurerm_monitor_diagnostic_setting #12246

Closed

This was referenced Feb 11, 2022

Retention Policy of Azure Activity Logs Diagnostic Settings are being discarded #13470

Closed

azurerm_monitor_diagnostic_setting with dynamic always updates resource #13915

Closed

tombuildsstuff added the duplicate label Mar 21, 2022

tombuildsstuff mentioned this issue Mar 21, 2022

azurerm_monitor_diagnostic_setting updating metric and logs on each terraform plan / apply #15906

Closed

tombuildsstuff added question and removed bug labels Mar 21, 2022

tombuildsstuff mentioned this issue Mar 21, 2022

Cannot create or modify azurerm_monitor_diagnostic_setting #15046

Closed

tombuildsstuff added upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR and removed duplicate labels Mar 21, 2022

johannespetereit mentioned this issue Apr 1, 2022

Order of Application Gateway Configuration Blocks Should be Irrelvant #6896

Closed

stephybun mentioned this issue Apr 8, 2022

Changes for azurerm_monitor_aad_diagnostic_setting on every terraform apply #16197

Closed

1 task

teowa mentioned this issue Aug 23, 2022

azurerm_monitor_diagnostic_setting continues to see drift after apply #17172

Open

1 task

teowa mentioned this issue Nov 14, 2022

azurerm_monitor_diagnostic_setting continuously overwriting same values for diagnostics #19258

Closed

1 task

rcskosir added the v/2.x (legacy) label Oct 10, 2023

rcskosir added v/3.x upstream/microsoft/blocking-api-issue This label is applicable when there is a bug on the Azure API that is blocking. and removed upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR labels Mar 18, 2024

jarpoole mentioned this issue Apr 26, 2024

Provider produced inconsistent final plan in azurerm_monitor_diagnostic_setting #25435

Open

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

azurerm_monitor_diagnostic_setting re-applies changes/updates every time running plan or apply... #10388

azurerm_monitor_diagnostic_setting re-applies changes/updates every time running plan or apply... #10388

kon1180 commented Jan 29, 2021 •

edited

Loading

This comment has been minimized.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

flo-02-mu commented Dec 29, 2021

PPACI commented Feb 7, 2022

SenorRagequit commented Feb 23, 2022

biswarup1290dass commented Feb 25, 2022 •

edited

Loading

murdibb commented Mar 14, 2022

or-shachar commented Mar 16, 2022

MageshSrinivasulu commented Mar 31, 2022

guidooliveira commented Aug 8, 2022

kamilzzz commented Feb 16, 2023

mtrin commented Feb 21, 2023

mukeshinit commented May 15, 2023 •

edited

Loading

shanilhirani commented Jun 19, 2023 •

edited

Loading

Stolz commented Oct 20, 2023

Kulesza commented Dec 25, 2023 •

edited

Loading

azurerm_monitor_diagnostic_setting re-applies changes/updates every time running plan or apply... #10388

azurerm_monitor_diagnostic_setting re-applies changes/updates every time running plan or apply... #10388

Comments

kon1180 commented Jan 29, 2021 • edited Loading

Community Note

Terraform (and AzureRM Provider) Version

Affected Resource(s)

Expected Behaviour

Actual Behaviour

Steps to Reproduce

Code

This comment has been minimized.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

This comment was marked as off-topic.

flo-02-mu commented Dec 29, 2021

PPACI commented Feb 7, 2022

SenorRagequit commented Feb 23, 2022

biswarup1290dass commented Feb 25, 2022 • edited Loading

murdibb commented Mar 14, 2022

or-shachar commented Mar 16, 2022

MageshSrinivasulu commented Mar 31, 2022

guidooliveira commented Aug 8, 2022

kamilzzz commented Feb 16, 2023

mtrin commented Feb 21, 2023

mukeshinit commented May 15, 2023 • edited Loading

shanilhirani commented Jun 19, 2023 • edited Loading

Stolz commented Oct 20, 2023

Kulesza commented Dec 25, 2023 • edited Loading

kon1180 commented Jan 29, 2021 •

edited

Loading

biswarup1290dass commented Feb 25, 2022 •

edited

Loading

mukeshinit commented May 15, 2023 •

edited

Loading

shanilhirani commented Jun 19, 2023 •

edited

Loading

Kulesza commented Dec 25, 2023 •

edited

Loading