feat: implement container network attaching

Containers can be attached:

- after they are created, but before they are started
- after a successful deploy, but before the proxy reloads

This allows folks to have flexibility around when they would like a container to be made available to a network.

plugins/network/src/subcommands/subcommands.go

@@ -17,6 +17,38 @@ func main() {
 	flag.Parse()
 
 	switch subcommand {
+	case "create":
+		networkName := flag.Arg(1)
+		err := network.CommandCreate(networkName)
+		if err != nil {
+			common.LogFail(err.Error())
+		}
+	case "destroy":
+		networkName := flag.Arg(1)
+		forceDestroy := false
+		if flag.Arg(2) == "force" {
+			forceDestroy = true
+		}
+		err := network.CommandDestroy(networkName, forceDestroy)
+		if err != nil {
+			common.LogFail(err.Error())
+		}
+	case "exists":
+		networkName := flag.Arg(1)
+		err := network.CommandExists(networkName)
+		if err != nil {
+			common.LogFail(err.Error())
+		}
+	case "info":
+		err := network.CommandInfo()
+		if err != nil {
+			common.LogFail(err.Error())
+		}
+	case "list":
+		err := network.CommandList()
+		if err != nil {
+			common.LogFail(err.Error())
+		}
 	case "rebuild":
 		appName := flag.Arg(1)
 		network.BuildConfig(appName)

plugins/network/src/triggers/triggers.go

@@ -63,12 +63,22 @@ func main() {
 	case "post-app-clone-setup":
 		appName := flag.Arg(1)
 		network.TriggerPostAppCloneSetup(appName)
+	case "post-container-create":
+		containerType := flag.Arg(0)
+		containerID := flag.Arg(1)
+		appName := flag.Arg(2)
+		phase := flag.Arg(3)
+		processType := flag.Arg(4)
+		network.TriggerPostContainerCreate(containerType, containerID, appName, phase, processType)
 	case "post-create":
 		appName := flag.Arg(0)
 		network.TriggerPostCreate(appName)
 	case "post-delete":
 		appName := flag.Arg(0)
 		network.TriggerPostDelete(appName)
+	case "core-post-deploy":
+		appName := flag.Arg(0)
+		network.TriggerCorePostDeploy(appName)
 	case "report":
 		appName := flag.Arg(0)
 		network.ReportSingleApp(appName, "")