Files
HAL9000 93f6cc703c
CI / push-validation (pull_request) Successful in 29s
CI / helm (pull_request) Successful in 42s
CI / lint (pull_request) Successful in 50s
CI / build (pull_request) Successful in 52s
CI / quality (pull_request) Successful in 53s
CI / typecheck (pull_request) Successful in 58s
CI / security (pull_request) Successful in 1m32s
CI / unit_tests (pull_request) Successful in 6m15s
CI / docker (pull_request) Successful in 1m38s
CI / integration_tests (pull_request) Successful in 10m5s
CI / coverage (pull_request) Successful in 12m43s
CI / status-check (pull_request) Successful in 3s
fix(tests): use valid ULID and classification in clone-into step fixture
Resource Pydantic model requires resource_id to match the ULID pattern
^[0-9A-HJKMNP-TV-Z]{26}$ and classification to be 'physical' or
'virtual'. The test fixture used '01HANDLER0000000000000001' (invalid
ULID) and 'tool' (invalid enum), causing a ValidationError during
scenario setup that Behave reported as a traceback outside scenario.

Fixes the errored scenario in features/container_clone_into.feature:88.

ISSUES CLOSED: #7555
2026-06-02 20:37:35 -04:00
..