gitops-pusher: friendlier error on invalid subcommand

If an invalid subcommand was provided to the gitops-pusher (e.g. I
mistakenly passed 'sync' rather than the expected 'apply'), the error
rendered from ffcli does not make this obvious to the operator,
particularly when rendered in a CI pipeline. The error was:

terminal command () doesn't define an Exec function

This trivial change catches the ffcli error and provides a friendlier
error to the user to hopefully aid their diagnosis of the problem in
these cases.

Fixes #11842.

Signed-off-by: Matthew Huxtable <git@tigermatt.uk>

cmd/gitops-pusher/gitops-pusher.go

@@ -11,6 +11,7 @@ import (
 	"context"
 	"crypto/sha256"
 	"encoding/json"
+	"errors"
 	"flag"
 	"fmt"
 	"log"
@@ -216,6 +217,14 @@ func main() {
 	}
 
 	if err := root.Parse(os.Args[1:]); err != nil {
+		if noexec := (ffcli.NoExecError{}); errors.As(err, &noexec) {
+			if args := noexec.Command.FlagSet.Args(); len(args) > 0 {
+				log.Fatalf("invalid subcommand %s, see -help for available subcommands", args[0])
+			} else {
+				log.Fatal("missing subcommand, see -help for available subcommands")
+			}
+		}
+
 		log.Fatal(err)
 	}