Closed thatmidwesterncoder closed 9 months ago
Fields that existed in the terraform provider were not used by rancher, namely the keypair_name fields from the openstack and aws providers.
The fields were removed from the terraform provider.
Terraform RC v4.0.0-rc2. Just sanity checking to make sure the provider still works. Since the fields weren't working before it shouldn't effect anything.
N/A
No repro steps necessary.
For testing - use the v3.2.0-rc3
release.
Waiting for v4.0.0-rc2
thaneunsoo said: Closing this issue based on this comment https://github.com/rancher/terraform-provider-rancher2/issues/1192#issuecomment-1737900287
This is a backport for https://github.com/rancher/terraform-provider-rancher2/issues/1192
Original Issue below:
Other details Underlying Infrastructure: AWS Downstream clusters bootstrapped with Terraform
Issue description The
keypair_name
argument appears to not be supported in the context of Rancher provisioning EC2. Comparing with previous issues (1, 2, 3) and rancher/machine this argument in the documentation for the terraform provider can add confusion.Expected behavior: Non implemented features should be removed from documentation