Update replace kubeconfig token logic

[a-blender]

Issue: #841

Problem

When using TF output or data resources that changes after the apply, all subsequent runs of terraform plan creates a new kubeconfig API token until terraform apply is run again to get the output and data changes. This was seen on both Rancher 2.6.9 and 2.6.10.

Solution

After investigation, the root cause of this issue is likely that Terraform downloads / generates a kubeconfig on every run of a terraform plan or apply. TF replaces the kubeconfig token every time instead of using the token from the cached kubeconfig, which is causing the over generation of API tokens.

My solution is to update the getClusterKubeconfig logic explained here to use the API token from the cached kubeconfig (if it exists) instead of always replacing it.

Testing

Engineering Testing

Manual Testing

@jakefhyde I was unable to reproduce this behavior again on 2.6.10 using the customer's lab setup, but was also not seeing the token over generation when testing on my fork.

Test plan

• Verify new API tokens are not created on a terraform plan after the first terraform apply on latest rancher v2.6 with local fix
• Verify same behavior on latest rancher v2.7 (rainbow)

Automated Testing

QA Testing Considerations

Regressions Considerations