Update supported versions in documentation #646
Conversation
Signed-off-by: Brian Presley <[email protected]>
sumobrian
requested review from
AndreKurait,
chelma,
gregschohn,
lewijacn,
mikaylathompson,
okhasawn and
peternied
as code owners
| |Supported Sources|Supported Targets|Source Platform|Target Platform| | ||
| |:---------------:|:---------------:|:-------------:|:-------------:| | ||
| |ElasticSearch 7-7.10.2|OpenSearch 1.x and 2.x|AWS Self-Managed|AWS OpenSearch and OpenSearch Serverless| | ||
| There are numerous combinations of source clusters, target clusters, and platforms. While the tools provided in this repository might work with various combinations, they might not support breaking changes between different source and target versions. Below is a list of supported source and target versions and platforms. |
There was a problem hiding this comment.
what does "might not support breaking changes" mean?
There was a problem hiding this comment.
Users need to run test to determine that there are no breaking changes. If there are breaking changes, they will have to make changes to drop breaking changes or transform breaking changes.
| ### Supported Source and Target Platforms | ||
| * Self-managed (hosted by cloud provider) | ||
| * Self-managed (on-premises) | ||
| * Managed cloud offerings (e.g., Amazon OpenSearch, Amazon OpenSearch Serverless) |
There was a problem hiding this comment.
Serverless won't work w/ RFS. That may be good to call out.
| |ElasticSearch 7-7.10.2|OpenSearch 1.x and 2.x|AWS Self-Managed|AWS OpenSearch and OpenSearch Serverless| | ||
| There are numerous combinations of source clusters, target clusters, and platforms. While the tools provided in this repository might work with various combinations, they might not support breaking changes between different source and target versions. Below is a list of supported source and target versions and platforms. | ||
|
|
||
| ### Supported Source and Target Versions |
There was a problem hiding this comment.
I like this view better, but I think that once we have integ tests in place, it will be really nice to list a table of specific combinations that we're testing. So, this works for now and later but I'd like to see the table (or a link to one) come back in in the coming weeks as we add tests.
There was a problem hiding this comment.
I would love to see that. I've been discussing this with @lewijacn
Description
[Describe what this change achieves]
Refresh on supported version lsit.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.