Add stronger warning against attempting a shared tier upgrade #516
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
Users who attempt to upgrade from a shared tier cluster (M2/M5) to a dedicated tier cluster - even though it is called out as unsupported - will destroy the shared tier and create a dedicated tier. This is due to the fact that upgrades are not supported yet Terraform will still try to make the changes it sees in the config. Adding stronger language to the call out that this is not supported since it will result in data lost from the shared tier cluster.
Link to any related issue(s):
Type of change:
Required Checklist:
Further comments