fix: render EKS Kubernetes exec authentication as a provider block

[alongubkin]

What changed

Render EKS exec authentication as a nested block in the standalone Kubernetes Terraform provider. Keep the object form required by Helm 3's kubernetes attribute. The two provider schemas accept different HCL forms, so sharing one representation generated an invalid Kubernetes provider configuration.

Validation

• cargo fmt -p alien-terraform --check
• cargo test -p alien-terraform --lib (58 passed)
• New provider test runs real terraform init -backend=false and terraform validate for the generated EKS Kubernetes and Helm provider configurations.

Related: ALIEN-995.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; no actionable issue was identified.

Summary

The PR renders EKS exec authentication in the distinct HCL forms required by the standalone Kubernetes and Helm providers.

• Adds a Terraform validation test covering both generated provider configurations.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  EKS[EKS authentication fields] --> K[Kubernetes provider]
  EKS --> H[Helm provider]
  K --> B["exec { ... } block"]
  H --> O["kubernetes = { exec = { ... } }"]

Loading

_{Reviews (1) · Last reviewed commit: "fix(terraform): render EKS Kubernetes ex..."}