Executor equivalent of "nx run ..." cli command?

[callajd]

Hi, I'm trying to create a target that simply runs other targets as dependencies, what I'm calling a "rollup" target.

It seems like this target shouldn't require its own executor since it doesn't do anything itself, just
executes other targets in correct order. E.g., something like the deploy target below:

{
  "name": "cloud",
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "sourceRoot": "apps/cloud",
  "projectType": "application",
  "targets": {
    "build": {
      "executor": "@nx/next:build", 
      "dependsOn": [{
        "projects": ["prisma"],
        "target": "generate"
      }]
    },
    "container": {
      "executor": "@library/service:container",
      "dependsOn": ["^build"],
      "options": {
        "tags": ["DEVELOP"],
        "push": false
      },
      "configurations": {
        "snapshot": {
          "tags": ["SNAPSHOT"]
        },
        "production": {
          "tags": ["PRODUCTION"]
        }
      }
    },
    "deploy": {
      "configurations": {
        "snapshot": {
          "dependsOn": [
            "container:snapshot",
            {
              "projects": ["stacks"],
              "target": "deploy:cloud:snapshot"
            }
          ]
        },
        "production": {
          "dependsOn": [
            "container:production",
            {
              "projects": ["stacks"],
              "target": "deploy:cloud:production"
            }
          ]
        }
      }
    }
  }
}

But nx cli doesn't recognize the deploy target when written this way:

~/code/actuate/web > nx run cloud:deploy:snapshot --verbose

 NX   Cannot find configuration for task cloud:deploy

Error: Cannot find configuration for task cloud:deploy
    at ProcessTasks.createTask (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/tasks-runner/create-task-graph.js:159:19)
    at ProcessTasks.processTasks (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/tasks-runner/create-task-graph.js:36:39)
    at createTaskGraph (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/tasks-runner/create-task-graph.js:198:21)
    at createTaskGraphAndRunValidations (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/tasks-runner/run-command.js:78:63)
    at ensureWorkspaceIsInSyncAndGetGraphs (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/tasks-runner/run-command.js:132:21)
    at runCommandForTasks (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/tasks-runner/run-command.js:114:47)
    at /Users/jefferycallahan/code/actuate/web/node_modules/nx/src/tasks-runner/run-command.js:105:35
    at handleErrors (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/utils/handle-errors.js:8:30)
    at runCommand (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/tasks-runner/run-command.js:104:59)
    at Object.runOne (/Users/jefferycallahan/code/actuate/web/node_modules/nx/src/command-line/run/run-one.js:48:59)

It seems like the target is only recognized when I add an executor to its definition so I tried the nx:noop executor but (true to its name) it seems like a real no op.

What I'm really looking for is an executor that behaves like nx run on the CLI.

This seems like such an obvious thing I must be missing something but I can't seem to get it working short of executing a raw command or writing a custom executor, neither of which seem right. What am I doing wrong here?