Achieve feature parity with the talosctl CLI

[obvionaoe]

Currently, while the Terraform provider is very useful, it has quite a few shortcomings. I think it'd be of great interest to track what use cases can be currently achieved by using the CLI but not with Terraform and target them for future update of the provider.

Cases:

• The use case I've come across the most is when applying configuration patches after the first apply the talos_machine_configuration_apply ignores all changes to the config_patches list argument. This means that we cannot patch the nodes using Terraform and must either use the CLI or completely recreate the cluster using Terraform.
• Another use case is triggering updates to the cluster as mentioned in this issue gracefull upgrades through terraform #140 .

It'd be a great improvement if these use cases could be implemented into the provider. Please feel free to contribute to this list.

Thanks

[ionfury]

I am experimenting with the Talos terraform provider provider. I would like to be able to use terraform test to validate my cluster and machine configuration. Because the configuration is applied via config_patches in talos_machine_configuration_apply, I don't see a straightforward way to use native terraform/tofu tests to validate configured machines.

The talosctl CLI can be used to query the configured machines directly and combined with terratest, but this does not lend itself to the clean simplicity of the terraform test approach.

I would really appreciate more talosctl get functionality exposed via the terraform provider data sources to facilitate a straightforward terraform test implementation.