Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
UUID validation of jobRef breaks bulk import of jobs in clean instance of RunDeck #4471
We often have to build out new instances of RunDeck from scratch from a set of templates that include a number of projects and jobs as part of our development workflow with the tool. As part of this build process a new, clean instance of RunDeck is spun up, and project / job data is imported from an archive created using the rd cli tool.
The tools first create the projects from the exported data, they then iterate over each project in turn and import the yaml associated with each job for each project. Prior to v3.0.13 this import did no checking of UUID integrity, so would succeed in importing the jobs no matter what order this is done. I think that the following changes introduced UUID checking for jobRefs:
This breaks the job import into a clean system unless we import the jobs in the reverse order to when they are referenced. We have hundreds of jobs with many references between them over multiple projects so working out the order is going to be difficult, is there any way that we can import the data ignoring the jobRef UUID checks given that the data will have been exported from a known good working system?
My Rundeck detail
This results in the error :
Jobs can be imported without the need for me to work out the order for which they have to be imported (we have hundreds of jobs with dependencies on others).