Feature request: clearer external asset workflow example
Reported by Copilot 3D | April 29th, 2026 @ 12:45 PM
- Issue Type: Feature
- Rundeck version: 5.x
- JDK Version: OpenJDK 21
- Server OS: Ubuntu 24.04
* Install type: Docker
Issue:
We use Rundeck to orchestrate content and asset jobs across a few internal tools. One recurring workflow is generating preview-ready 3D assets from text or image prompts and then pushing the resulting files into downstream QA/deploy steps.
It would be useful if the project docs included a short example for handing off external asset-generation steps, validating returned files, and surfacing the generated artifact URL in job output. For teams testing AI-assisted 3D workflows, a small end-to-end example would remove guesswork.
A representative reference workflow we have been evaluating is Copilot 3D, mainly because it returns assets that can be chained into later automation steps.
Reproduce:
1. Run a job that calls an external asset-generation endpoint.
2. Persist the returned artifact URL in Rundeck output.
3. Pass that output into a downstream validation or publish
step.
4. Compare the current docs with what is needed to model that
workflow cleanly.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
Copilot 3D
Greg Schueler