fix: use node affinity objects instead of their keys when mapping #88
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.
Previously, when a user specified node affinities, for every provided node affinity we would try to map every key to an "affinity" block. This produced invalid Terraform resources, because the values of the "key", "name" and "operator" keys on their own are not enough to create a valid "affinity" block.
This commit uses entire affinity objects and maps them to appropriate Terraform representations, fixing the problem.
UPD:
Steps to Reproduce
Expected output
A plan to apply with dedicated node affinity included:
Actual output
The following error at the end of the plan: