Observed Generation Not Set to -1, Causing Incorrect Readiness Status

[chanwit]

The observed generation is not set to -1 in the Terraform object's status, causing Kubernetes kstatus to consider it ready even when it is still applying.

When a Terraform resource is created, its status does not have the observed generation set to -1. This results in Kubernetes kstatus considering the Terraform resource as ready, even though it is still in the process of applying changes.

1. Code reference in GitRepository types: https://github.com/fluxcd/source-controller/blob/main/api/v1/gitrepository_types.go#L270
2. Code reference in Terraform types: https://github.com/weaveworks/tf-controller/blob/main/api/v1alpha2/terraform_types.go#L402
3. Example usage in Kustomization Controller: https://github.com/fluxcd/kustomize-controller/blob/main/internal/controller/kustomization_controller.go#L172

---

Acceptance Criteria

• Upon creation of a Terraform resource, the observedGeneration should be initialized to -1.
• Once the Terraform resource has successfully applied changes, kstatus should recognize it as ready.
• LastHandledReconcileAt should contain a proper timestamp value.

[lasomethingsomething]

Proposed ACs:

• The observed generation status of a Terraform resource is set to -1 upon resource creation.
• The Flux runtime package applies an observedGeneration on each condition each time it observes that condition for that generation.