Support configuring late-initialization behavior during code-generation pipelines

[ulucinar]

What problem are you facing?

When trying #77 with provider-tf-azure on a v1alpha1.KubernetesCluster resource, it turns out that tfstate contains both:

"kubelet_identity": [
          {
            "client_id": "...",
            "object_id": "...",
            "user_assigned_identity_id": "..."
          }
        ]

and

"identity": [
              {
                "principal_id": "...",
                "tenant_id": "...",
                "type": "SystemAssigned",
                "user_assigned_identity_id": ""
              }
            ]

And the late initialization logic initializes both arrays with a zero-valued Identity[0].UserAssignedIdentityID, which is not allowed.

How could Terrajet help solve your problem?

We need to be able to configure late-initialization behavior of certain Terraformed resources via the resource configuration machinery.