Sebastian

@a8m trying to tag you directly :)

After actually spending some time with a decompiled template, I should add that this is actually not just "not looking nice" but really confusing: When you then want to refer...

doesn't it already?! I used it and that's the thing it made it usable after all ;)

hmm but since all the other resources of the cluster also get deleted, what is the point in keeping the PLS? At that point it cannot be recovered anymore

I might be wrong, but I would assume as the owner of the PLS (which AKS is), you have all the permissions to revoke/delete any Private Endpoint **Connections** I do...

any update on this @feiskyer? I still strongly believe AKS deletion should not get stuck on this

hm ok I see. But what is the reasoning behind this? As the cluster deletion itself is not being stopped, any other resources become stale and are not recoverable anyway.

@WodansSon I have done a custom build on your branch and did test it on my env in various forms. Not using the rules engine or the secret validator but...

Actually, testing this I found a (related bug): azurerm_cdn_frontdoor_origin has a field `health_probes_enabled`. However, that field should only exist on `azurerm_cdn_frontdoor_origin_group`. On the other side, the origin is totally missing...

I'd also be interested to see this running on Azure :)