Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix type assertion bug caused by non-existent k8s_surge_node_count #212

Merged
merged 1 commit into from
Oct 18, 2022

Conversation

nvthongswansea
Copy link
Member

Changes:

  • Check if k8s_surge_node_count can be asserted into float64. If so, set the resource parameter surge_node; o.w, don't set that parameter.

@nvthongswansea nvthongswansea self-assigned this Oct 18, 2022
surgeNodeCount := props.Parameters["k8s_surge_node_count"].(float64)
nodePool["surge_node"] = surgeNodeCount > 0
if surgeNodeCount, ok := props.Parameters["k8s_surge_node_count"].(float64); ok {
nodePool["surge_node"] = surgeNodeCount > 0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the value of nodePool["surge_node"] if k8s_surge_node_count was not? In other words, the condition is failed @nvthongswansea

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@itakouna if the condition is not met, the default value (true) of the surge_node will be set.

@nvthongswansea nvthongswansea merged commit 45e6957 into master Oct 18, 2022
@nvthongswansea nvthongswansea deleted the bug/k8s-param-assertion-failure branch September 25, 2024 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants