Repository navigation
Remove image and registry info from PO analysis start request - #232
Conversation
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
Merge PrivateAIM/node-hub-api-adapter#232?Waiting for approval until 2026-10-29T13:19:23.533Z. Approve or deny: https://maintainer.placzek.dev/ui/approvals?run=bfdf60dd-5bec-48af-ade8-6e895cecb257&approval=1%3Acall_3fc5cf81c744448d837cf34b19098a8c%3A0 |
|
perfect! |
There was a problem hiding this comment.
🔇 Additional comments: 1
hub_adapter/routers/podorc.py-48-50: 1
48-50:Minor · Potential issue · Heavy lift
⚠️ Unverified finding
We couldn't verify this from the code. It is shown for review, not as a verified issue.Removing registry credentials makes a successful private-image start depend on the PO obtaining credentials by another means, even if it accepts the reduced request.
The pod cannot pull its image and the analysis does not start.
This can occur when: An analysis uses a private registry whose pull credentials were previously supplied in the start request.

Review info
-
Run configuration-
- Source mode: Auto
- Repository: Unavailable
- Branch: Unavailable
- File: No configuration file from this repository applied
- Commit: Unavailable
- Layers: defaults
- Review profile: CHILL
- Plan: Advanced
- Run ID:
e92affd3-65db-4173-aa6b-760c3f96e903
Files selected for processing: 6-
hub_adapter/autostart.pyhub_adapter/constants.pyhub_adapter/routers/podorc.pytests/constants.pytests/test_autostart.pytests/test_dependencies.py
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
-
Merge PrivateAIM/node-hub-api-adapter#232?Waiting for approval until 2026-10-30T13:19:53.287Z. Approve or deny: https://maintainer.placzek.dev/ui/approvals?run=24709c41-7edb-4854-9ddf-2c0f16382e10&approval=1%3Acall_64b9240b1ff84d5d8e9d175894292774%3A0 |
Summary by CodeRabbit
includevalues.