fix : set desired_nodes without max_nodes and min_nodes #538
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When you want to create a nodepool, if you don't specify the max_nodes parameter, it is set to "0".
When you call the nodepool creation, the desired_nodes can not be greater than the max_nodes, and so it is set to "0".
The nodepool is created with 0 node.
The payload of the request must contain only the parameters specify in the hcl nodepool resource.
Fixes #485 (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
make testacc TESTARGS="-run TestAccCloudProjectKubeNodePoolRessource"
make testacc TESTARGS="-run TestAccCloudProjectKubeNodePool"
Test Configuration:
terraform version
: Terraform v1.6.6Checklist: