bug4811: refactored UpgradeAmi procedure and continued with its snapshot handling

This commit is contained in:
Axel Uhl
2020-11-06 18:46:49 +01:00
parent 92afc436a0
commit 8e8d51c64e
13 changed files with 303 additions and 178 deletions
@@ -24,6 +24,7 @@ import com.sap.sailing.landscape.SailingAnalyticsMetrics;
import com.sap.sailing.landscape.SailingAnalyticsReplica;
import com.sap.sailing.landscape.impl.BearerTokenReplicationCredentials;
import com.sap.sailing.landscape.procedures.StartSailingAnalyticsMaster;
import com.sap.sailing.landscape.procedures.UpgradeAmi;
import com.sap.sse.common.Duration;
import com.sap.sse.common.TimePoint;
import com.sap.sse.landscape.InboundReplicationConfiguration;
@@ -67,6 +68,20 @@ public class TestProcedures {
securityServiceReplicationBearerToken = System.getProperty(SECURITY_SERVICE_REPLICATION_BEARER_TOKEN);
}
@Test
public void testImageUpgrade() throws Exception {
final com.sap.sailing.landscape.procedures.UpgradeAmi.Builder<String, SailingAnalyticsMaster<String>, SailingAnalyticsReplica<String>> imageUpgradeProcedureBuilder = UpgradeAmi.builder();
final UpgradeAmi<String, SailingAnalyticsMaster<String>, SailingAnalyticsReplica<String>> imageUpgradeProcedure =
imageUpgradeProcedureBuilder.build();
try {
imageUpgradeProcedure.run();
int continueHere;
// TODO add test verdicts
} finally {
imageUpgradeProcedure.getUpgradedAmi().delete();
}
}
@Test
public void testMongoReplica() throws Exception {
final Builder<String, ApplicationProcessMetrics, ?, ?> startMongoDBServerProcedureBuilder = StartMongoDBServer.builder();