Chain workflows by repository_dispatch?

[ckeller-microstar]

Select Topic Area

Question

Body

My use case is that I'm attempting to support two CI/CD workflows. I have two separate workflow_dispatch jobs for build+upload and deploy. For production deployments we want those jobs separated so we can prep resources and then swap them quickly, but for development environments, I'd like to chain those two actions, one after another.

My first approach was to include in the build+upload job's workflow_dispatch inputs a boolean to specify whether to trigger the deploy workflow afterward. When enabled, this would use peter-evans/repository-dispatch@v3 to trigger the deploy job, which could be triggered by on: repository_dispatch. I got pretty far prototyping that, but ultimately got this error in build+upload when using the repository-dispatch action:

Upload JARs at chain-upload-deploy to AWS dev
Resource not accessible by integration

At this point I switched gears to using two reusable workflow_call workflows with the bulk of each action (build+upload and deploy) with three workflow_dispatch jobs (build+upload only, deploy only, and both) to kick off the relevant sub-jobs, and I made a separate post about the issue I'm facing there. But, at a high level, does using repository_dispatch seem like a reasonable approach to the problem, or should I abandon this?