[BUG] ovh_cloud_project_kube
requires load_balancers_subnet_id
but doesn't properly update it on the resource
#683
Labels
Product: Managed Kubernetes Service
Status: Coming Soon
The feature will hit GA usually in less than 2 months
Type: Bug
Describe the bug
After upgrading the provider from 0.43.1 to 0.46.1, a plan on our
ovh_cloud_project_kube
resource resulted in the following error:The used configuration looked like this:
I modified the resource, to include the
load_balancers_subnet_id
as follows:Then running
plan
andapply
successfully finishes. But when running a plan afterwards, the resource wants to update again:Here I'd expect no changes to be planned.
First of all, from the documentation it's unclear to me, that
load_balancers_subnet_id
is required, whenprivate_network_id
is set, the last example in the documentation even uses theprivate_network_id
without theload_balancers_subnet_id
. It's also slightly unclear to me, which effect theload_balancers_subnet_id
will have, though I assume it's not about the external IP of the loadbalancer. Though then I'd assume thenodes_subnet_id
should be used here?Secondly, applying the change to
load_balancers_subnet_id
doesn't actually seem to have an effect.Terraform Version
OpenTofu v1.7.0-alpha1
OVH Terraform Provider Version
v0.46.1
Affected Resource(s)
Terraform Configuration Files
relevant part is:
Expected Behavior
load_balancers_subnet_id
should actually be required when usingprivate_network_id
. Documentation should reflect this requirement.load_balancers_subnet_id
and not produce planned changes on every run.Actual Behavior
Regarding 1 using
private_network_id
withoutload_balancers_subnet_id
produces an error.Regarding 2, the resource is unchanged after applying.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan -out planfile
on the first configuration. Error should appearload_balancers_subnet_id
to configurationterraform plan -out planfile
should work without errorsterraform apply planfile
should run succesfullyterraform plan -out planfile
will plan the change on the resource againThe text was updated successfully, but these errors were encountered: