Looping over databases to create SQL logins and users in Terraform for Azure causes authentication errors. Revised snippet:
resource "azsql_login" "lg" { for_each = var.dbList; fqdn = azsql_server.main.fqdn; login = "lg-${each.key}"; pass = "Secret123!" }
resource "azsql_user" "us" { for_each = var.dbList; db = each.key; name = "user_${each.key}"; roles = ["read", "write"]; depends_on = [azsql_login.lg] }
Based on previous experiences managing similar setups, it is crucial to validate that all dependency relationships are explicitly defined. In cases where loop-based resource creation led to authentication issues, I found that ensuring the full completion of SQL login creation before progressing to user creation was essential. This often involved managing subtle timing issues and verifying that each resource was fully provisioned before referencing it in related tasks. Additionally, validating that the login parameters meet the specific SQL server’s requirements proved valuable. Paying close attention to these details during testing can prevent authentication errors when automating the setup process with Terraform.
hey, i’ve seen similiar issues. splitting resource creation can fix ordering mishaps. for each loops sometimes cause race conditions that lead to auth errors. check if your login params fit azure reqirements and set depndencies clearly.
hey, have you rechecked if azure’s propagation time might be affecting the login setup? i had a similar hiccup and found that a slight delay after creating resources helped. could it be an intermittent delay issue, or do u think its something else in the loop logic?