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

feat: defaults when node_count is 1 #859

Merged
merged 1 commit into from
Apr 5, 2023
Merged

feat: defaults when node_count is 1 #859

merged 1 commit into from
Apr 5, 2023

Conversation

blgm
Copy link
Member

@blgm blgm commented Apr 5, 2023

When node_count == 1, the multi_az_enabled and
automatic_failover_enabled properties must be false. During testing of upgrades, we found that this could be problematic for automatic_failover_enabled.

In previous versions automatic_failover_enabled was false when node_count was 1 and true otherwise. It was not exposed as a property.

We had a desire to expose automatic_failover_enabled and multi_az_enabled as properties, and to remove this defaulting behaviour so that users could be clear that when they set multi_az_enabled or automatic_failover_enabled it would apply, or there would be a failure.

But considering upgrades, there is a scenario where a plan allows the user to set the node_count. When upgrading this plan, so instances would need automatic_failover_enabled: false in order to upgrade successfully and some would not. The upgrade process does not allow properties to be changed, leading to a unhappy upgrade process.

So we decided that automatic_failover_enabled should be false when the node_count is 1. For consistency we have done the same for multi_az_enabled, although this property was not problematic.

#184869846

Checklist:

When node_count == 1, the multi_az_enabled and
automatic_failover_enabled properties must be false. During testing of
upgrades, we found that this could be problematic for
automatic_failover_enabled.

In previous versions automatic_failover_enabled was false when
node_count was 1 and true otherwise. It was not exposed as a property.

We had a desire to expose automatic_failover_enabled and
multi_az_enabled as properties, and to remove this defaulting behaviour
so that users could be clear that when they set multi_az_enabled or
automatic_failover_enabled it would apply, or there would be a failure.

But considering upgrades, there is a scenario where a plan allows the
user to set the node_count. When upgrading this plan, so instances would
need `automatic_failover_enabled: false` in order to upgrade
successfully and some would not. The upgrade process does not allow
properties to be changed, leading to a unhappy upgrade process.

So we decided that automatic_failover_enabled should be false when the
node_count is 1. For consistency we have done the same for
multi_az_enabled, although this property was not problematic.

[#184869846](https://www.pivotaltracker.com/story/show/184869846)
@jhvhs jhvhs merged commit 9077706 into main Apr 5, 2023
@jhvhs jhvhs deleted the unitynodecount branch April 5, 2023 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

2 participants