From 1ae8fcebabbdb62e55aa1df9f72bba7c3fc40d41 Mon Sep 17 00:00:00 2001
From: Mohsin Zaidi <2236875+smrz2001@users.noreply.github.com>
Date: Mon, 6 Nov 2023 09:55:45 -0500
Subject: [PATCH] fix(cd): check ceramic stability after rust-ceramic
 deployment

---
 cd/manager/jobs/deploy.go | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/cd/manager/jobs/deploy.go b/cd/manager/jobs/deploy.go
index f20efe8..8cedbe1 100644
--- a/cd/manager/jobs/deploy.go
+++ b/cd/manager/jobs/deploy.go
@@ -190,11 +190,11 @@ func (d deployJob) checkEnv() (bool, error) {
 	layout, _ := d.state.Params[job.DeployJobParam_Layout].(manager.Layout)
 	if deployed, err := d.d.CheckLayout(&layout); err != nil {
 		return false, err
-	} else if !deployed || (d.component != manager.DeployComponent_Ipfs) {
+	} else if !deployed || ((d.component != manager.DeployComponent_Ipfs) && (d.component != manager.DeployComponent_RustCeramic)) {
 		return deployed, nil
 	} else
-	// Make sure that after IPFS is deployed, we find Ceramic tasks that have been stable for a few minutes before
-	// marking the job complete.
+	// Make sure that after IPFS or rust-ceramic is deployed, we find Ceramic tasks that have been stable for a few
+	// minutes before marking the job complete.
 	//
 	// In this case, we want to check whether *some* version of Ceramic is stable and not any specific version, like we
 	// normally do when checking for successful deployments, so it's OK to rebuild the Ceramic layout on-the-fly each