Support transitions to/from dedicated masters by setting hot tier node_roles to unknown on topology size changes #682
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
Adds a plan modifier to ES topology elements, setting the hot tier node_roles to unknown if any topology size changes. This is to support transitioning to/from dedicated masters. It's hard to be more precise here, since we cannot known the eventual node count of a given plan without replicating potentially complicated sizing logic from the API to the provider.
Related Issues
Fixes #601
Related to #635
#635 discusses supporting master tiers without being defined in the TF module. Whilst the effort involved in doing that doesn't seem worthwhile (as above, we'd need to replicate cluster sizing logic into the provider), we may be able to support a zero sized master tier with size ignored on subsequent applies, which then becomes sized by Cloud autoscaling. I'm leaving #635 open to investigate better support there.
Motivation and Context
How Has This Been Tested?
Acceptance test, manually
Types of Changes
Readiness Checklist