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, we released a new patch version of dynamodb that introduced a new field called tableReplicas.
It turns out that updating to this change could trigger accidental deletion of table replicas that were previously/manually created or managed with different tools (such as CDK/CF). To smoothen the upgrade process, we propose to revert this change in a patch release, and re-introduce tableReplicas in a minor one, aligning more with semantic versioning standards and signaling to ACK users that a significant feature has been introduced so that they can read the change log and take the necessary actions.
We also propose that we create a standard/process around versioning, ideally new fields needs to be introduced in minor releases, patches should only include bug fixes and non-break behavior changes.
Description of changes:
tableReplica
field remains as a no-op fieldBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.