feat: implement coder exp boundary subcommand (#19771)

cli/exp_boundary.go

@@ -0,0 +1,12 @@
+package cli
+
+import (
+	boundarycli "github.com/coder/boundary/cli"
+	"github.com/coder/serpent"
+)
+
+func (*RootCmd) boundary() *serpent.Command {
+	cmd := boundarycli.BaseCommand() // Package coder/boundary/cli exports a "base command" designed to be integrated as a subcommand.
+	cmd.Use += " [args...]"          // The base command looks like `boundary -- command`. Serpent adds the flags piece, but we need to add the args.
+	return cmd
+}

cli/exp_boundary_test.go

@@ -0,0 +1,33 @@
+package cli_test
+
+import (
+	"testing"
+
+	"github.com/stretchr/testify/assert"
+
+	boundarycli "github.com/coder/boundary/cli"
+	"github.com/coder/coder/v2/cli/clitest"
+	"github.com/coder/coder/v2/pty/ptytest"
+	"github.com/coder/coder/v2/testutil"
+)
+
+// Actually testing the functionality of coder/boundary takes place in the
+// coder/boundary repo, since it's a dependency of coder.
+// Here we want to test basically that integrating it as a subcommand doesn't break anything.
+func TestBoundarySubcommand(t *testing.T) {
+	t.Parallel()
+	ctx := testutil.Context(t, testutil.WaitShort)
+
+	inv, _ := clitest.New(t, "exp", "boundary", "--help")
+	pty := ptytest.New(t).Attach(inv)
+
+	go func() {
+		err := inv.WithContext(ctx).Run()
+		assert.NoError(t, err)
+	}()
+
+	// Expect the --help output to include the short description.
+	// We're simply confirming that `coder boundary --help` ran without a runtime error as
+	// a good chunk of serpents self validation logic happens at runtime.
+	pty.ExpectMatch(boundarycli.BaseCommand().Short)
+}

cli/root.go

@@ -145,6 +145,7 @@ func (r *RootCmd) AGPLExperimental() []*serpent.Command {
 		r.promptExample(),
 		r.rptyCommand(),
 		r.tasksCommand(),
+		r.boundary(),
 	}
 }