Open Mikel-Landa opened 1 year ago
Managed to get it working after enabling management-policies in the sql provider and excluding LateInitialize
.
However, won't be closing the issue as I think this is just a workaround, especially taking into account the alpha status of management policies.
IMO it should have same default behavior as in terraform, e.g.
resource "azurerm_mssql_server" "this" {
name = "sql-${var.environment_name}-${var.unique_suffix}"
resource_group_name = var.resource_group_name
location = var.location
version = "12.0"
minimum_tls_version = "1.2"
azuread_administrator {
login_username = var.ad_admin_group.display_name
object_id = var.ad_admin_group.object_id
azuread_authentication_only = true
}
tags = var.tags
}
works out of the box in terraform, no need for ignore_changes and setting up initial values.
What happened?
On the azureadAdministrator -> azureadAuthenticationOnly setting:
However, when I configure the resource with the setting set to true, the status is the following:
Spec:
The resource stays on a Ready and Synced status of false, although the server is actually created on azure. Also I can see it dynamically added the field
administratorLogin
to the resource with an autogenerated value.How can we reproduce it?
Specify the
azureadAdministrator[0].azureadAuthenticationOnly
field but leaveadministratorLogin
andadministratorLoginPasswordSecretRef
blankWhat environment did it happen in?
Crossplane version: v1.13.2 Azure provider version: v0.36.0