software/theia: Fix publication conflicts

Export (theia0) and export (theia1, ...) instances published
connection parameters twice, once without and once with the
resiliency connection parameters. Keep only that last one.

software/theia/buildout.hash.cfg

@@ -23,11 +23,11 @@ md5sum = 9658a11340c018de816d0de40683706a
 
 [instance-import]
 _update_hash_filename_ = instance-import.cfg.jinja.in
-md5sum = c8d1be7aee980deb0f0d1a3126c9b9da
+md5sum = d0ff7b93e392f9b9233f9ae6ba81583f
 
 [instance-export]
 _update_hash_filename_ = instance-export.cfg.jinja.in
-md5sum = bb6d26c56b4bb9cf553c130fdd51000d
+md5sum = b982e83fa42103b7391d97eb36591174
 
 [instance-resilient]
 _update_hash_filename_ = instance-resilient.cfg.jinja

software/theia/instance-export.cfg.jinja.in

@@ -10,6 +10,10 @@ parts +=
   $${:theia-environment-parts}
   resilient-publish-connection-parameter
 
+# Avoid publication conflicts
+parts -=
+  publish-connection-parameter
+
 
 # The resilient stack makes the 'resilient' instance
 # request the 'export' instance with a 'namebase' parameter.

software/theia/instance-import.cfg.jinja.in

@@ -14,6 +14,10 @@ parts +=
   $${:theia-parts}
   $${:theia-environment-parts}
 
+# Avoid publication conflicts
+parts -=
+  publish-connection-parameter
+
 
 # The resilient stack makes the 'resilient' instance
 # request the 'import' instance with a 'namebase' parameter.