Support arbitrary ARM ID owners

This closes #2357. Nearly all resources now support being owned by an arbitrary ARM ID. Only database user resources (MySQLUser, PostgreSQLUser) do not allow ARM ID ownership. This is because those resources must extract certain connection information from their parents and so must have access to their parents via the Kubernetes API. ARM ID ownership behaves the following way: * Resources owned by an ARM ID will continue to attempt to reconcile if that ID doesn't exist. When the owning resource cannot be found, the resource will report a Ready=false with a "Warning" and additional details. If possible, avoid deleting the owning ARM resource without also deleting the resources in Kubernetes. * The credential being used for the resource must have the same subscription ID as the owning ARM resource. This means if your global credential is for Subscription A you cannot have ARM ID owners from subscription B unless you also create a serviceoperator.azure.com/credential-from for subscription B.
Azure · Sep 2, 2023 · 3ccb5ed · 3ccb5ed
1 parent 863737a
commit 3ccb5ed
Show file tree

Hide file tree

Showing 601 changed files with 8,337 additions and 3,758 deletions.
diff --git a/v2/api/appconfiguration/v1api20220501/configuration_store_types_gen.go b/v2/api/appconfiguration/v1api20220501/configuration_store_types_gen.go
diff --git a/v2/api/appconfiguration/v1api20220501storage/configuration_store_types_gen.go b/v2/api/appconfiguration/v1api20220501storage/configuration_store_types_gen.go
diff --git a/v2/api/appconfiguration/v1beta20220501/configuration_store_types_gen.go b/v2/api/appconfiguration/v1beta20220501/configuration_store_types_gen.go
diff --git a/v2/api/appconfiguration/v1beta20220501storage/configuration_store_types_gen.go b/v2/api/appconfiguration/v1beta20220501storage/configuration_store_types_gen.go
diff --git a/v2/api/authorization/v1api20200801preview/role_assignment_types_gen.go b/v2/api/authorization/v1api20200801preview/role_assignment_types_gen.go
diff --git a/v2/api/authorization/v1api20200801previewstorage/role_assignment_types_gen.go b/v2/api/authorization/v1api20200801previewstorage/role_assignment_types_gen.go
diff --git a/v2/api/authorization/v1beta20200801preview/role_assignment_types_gen.go b/v2/api/authorization/v1beta20200801preview/role_assignment_types_gen.go
diff --git a/v2/api/authorization/v1beta20200801previewstorage/role_assignment_types_gen.go b/v2/api/authorization/v1beta20200801previewstorage/role_assignment_types_gen.go
diff --git a/v2/api/batch/v1api20210101/batch_account_types_gen.go b/v2/api/batch/v1api20210101/batch_account_types_gen.go
diff --git a/v2/api/batch/v1api20210101storage/batch_account_types_gen.go b/v2/api/batch/v1api20210101storage/batch_account_types_gen.go
diff --git a/v2/api/batch/v1beta20210101/batch_account_types_gen.go b/v2/api/batch/v1beta20210101/batch_account_types_gen.go
diff --git a/v2/api/batch/v1beta20210101storage/batch_account_types_gen.go b/v2/api/batch/v1beta20210101storage/batch_account_types_gen.go
diff --git a/v2/api/cache/v1api20201201/redis_firewall_rule_types_gen.go b/v2/api/cache/v1api20201201/redis_firewall_rule_types_gen.go