Use UTC for scan timestamps and document ISO-8601 fields

[batzionb]

Summary

Scan started_at and completed_at are now produced with UTC (datetime.now(timezone.utc).isoformat()), and the Pydantic field descriptions on ScanInfoInput state that values are ISO-8601 with a UTC offset (e.g. ...+00:00).

Why this matters for clients

Without an explicit offset, timestamps from datetime.now().isoformat() are naive: they look like local wall-clock time but carry no timezone indicator, so API consumers cannot tell whether the value is UTC, local server time, or another zone. That breaks correct ordering, auditing, and display when clients are in different regions.

ISO-8601 strings from datetime.now(timezone.utc).isoformat() include a +00:00 suffix, so clients can reliably interpret the instant as UTC and convert to local time or compare with other UTC-normalized events.

Changes

• register.py: set started_at / completed_at using UTC-aware datetimes.
• exploit_iq_commons/data_models/input.py: document expected timestamp format on ScanInfoInput.

Made with Cursor

[zvigrinberg]

LGTM

[zvigrinberg]

/ok-to-test

[exploit-iq-pac]

Caution

There are some errors in your PipelineRun template.

PipelineRun

Error

vulnerability-analysis-on-pr

CEL expression evaluation error: expression "event == \"pull_request\" &&\n!body.pull_request.draft &&\n(target_branch == \"main\" || target_branch == \"rh-aiq-main\") &&\n(\"src/**\".pathChanged() || \"metrics_lib/**\".pathChanged() || \"pyproject.toml\".pathChanged() || \"uv.lock\".pathChanged() || \"Dockerfile\".pathChanged() || \".dockerignore\".pathChanged())\n" failed to evaluate: no such key: pull_request

[zvigrinberg]

/test vulnerability-analysis-on-pr