Hi Zac,
No problem at all!
For a CI/CD pipeline, you could use the site-driven scan CI driver. That will ultimately be the best way to achieve what you are trying to do.
In terms of triggering the scan without a schedule, you could use a mutation like below since schedule is not a required field:
mutation CreateScheduleItem {
create_schedule_item(input: {site_id: "24"}) {
schedule_item {
id
}
}
}
You will only need to change the site_id as appropriate in the example above. This will match an existing site with that ID in your Enterprise portal and use the associated scan configurations, scope, extensions, etc... that already exist for the site. This is essentially what the new site-driven scan CI driver does.
The required fields are followed by a '
!' in the documentation, for future reference.
Let me know if you have any more questions! :)