Create a Trent project for security scanning. Its first scan starts
automatically unless trigger_analysis is false, or a source is still
syncing in (sources or source_scopes); then start it with trigger_analysis,
which syncs any source that has not landed.
Supply at least one source: github_repo, website_url, or documents. For
documents, call prepare_file_upload, run upload_command, and pass s3_url.
Do not bundle source code into documents; connect its repository through
github_repo and the Trent GitHub App. For a quick plan review before
creating a project, use security_advisor.
The scan runs in the background and takes up to 1 hour. Read job_id, then
poll get_scan_status, with a first look around 10 minutes in. Relay any
returned 'Trent dashboard: <url>' line verbatim.
A matching repository or website returns reason='confirmation_needed'
with existing_project_details. Show the match and ask the user, then call
again with dedup_policy='reuse' or 'force_new'. A first call with
'force_new' requires the user's existing request for a new project.
If GitHub access prevents the scan starting, reason is
'github_app_install_required'. Send the user to the returned Trent GitHub
App install URL, then retry with trigger_analysis.
ConnectorOAuth