You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
All OpenSearch components should be running backwards compatibility tests to ensure compatibility as incrementing version numbers and modify features.
In the Security codebase as we are focusing on 2.1 the process to setup the cluster for BWC is hardcoded to allow for a single previous and current version. This prevent us from following the guidance to support BWC testing for 1.3.0 and 2.0.0 versions of OpenSearch and the Security plugin.
String bwcVersion ="1.3.0.0"; // Should be an array of versionsString baseName ="securityBwcCluster"String bwcFilePath ="src/test/resources/"String projectVersion ="2.0.0.0"2.times {i->
testClusters {
"${baseName}$i" {
testDistribution ="ARCHIVE"
versions = ["1.3.0","2.0.0"] // Bad practice that duplicates information
numberOfNodes =3
plugin(provider(newCallable<RegularFile>() {
@OverrideRegularFilecall() throwsException {
Expected behavior
We should have a better mechanism or central process to allow for appending additional versions of BWC tests as the version of the codebase increments.
Additional the distribution of these mechanism should be built into the gradle plugin that all component teams use so its easy to pick up and get updates as feature are added/introduced.
The text was updated successfully, but these errors were encountered:
Describe the bug
All OpenSearch components should be running backwards compatibility tests to ensure compatibility as incrementing version numbers and modify features.
In the Security codebase as we are focusing on
2.1
the process to setup the cluster for BWC is hardcoded to allow for a single previous and current version. This prevent us from following the guidance to support BWC testing for 1.3.0 and 2.0.0 versions of OpenSearch and the Security plugin.See bwc-test/build.gradle in the security codebase for the full implementation
Expected behavior
We should have a better mechanism or central process to allow for appending additional versions of BWC tests as the version of the codebase increments.
Additional the distribution of these mechanism should be built into the gradle plugin that all component teams use so its easy to pick up and get updates as feature are added/introduced.
The text was updated successfully, but these errors were encountered: