Terraform provider cannot update a virtual key that has no team

Finding: In an external report against LiteLLM v1.99.1 (ghcr.io/berriai/litellm:main-stable, image revision 10f4033437df30b91b5dbf2b64711d0a8683fc52, Postgres 16, Terraform v1.10.5), updating a virtual key that has no team through the Terraform provider fails with HTTP 500 and the message "Team object not found for team change validation" (https://github.com/BerriAI/litellm/issues/40704). Reported symptom: a litellm_key created without team_id applies fine, but changing max_budget from 10 to 25 and re-applying fails with error updating key and status 500. The reporter says the same edit works in the Admin UI, so Terraform state and the proxy drift apart (issue #40704). Reporter's isolation: a direct POST to /key/update with team_id set to an empty string returned 500 with the same error, while an equivalent update that omitted team_id returned 200 and the key kept team_id None (issue #40704). This suggests the empty-string team_id field triggers the failure on this version. Reporter hypothesis, not maintainer-confirmed: the Terraform provider sends team_id on every /key/update call, so a teamless key sends an empty string, and the proxy interprets this as a team change to a team named empty-string (issue #40704). The issue does not show provider source or proxy source confirming this; the cause is unconfirmed. Status: the issue was open as of the supplied data, with no maintainer comments, fix commit or released fix supplied. Fix status is unknown. Source-backed mitigation, not verified by KFA: when calling the API directly, omit team_id from /key/update for a teamless key, or edit the key in the Admin UI (issue #40704). This does not change what the Terraform provider sends. Limitations: this is a single external report, and KFA did not reproduce it. The version and environment come from the reporter. The Terraform provider version is not stated. Whether other versions are affected is unknown.