Migrate existing image logic to use ID-based actions
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 17h 7m
- Merged PRs (30d)
- 358
Description
## User Story
As a developer, I want to migrate existing canonical-based image operations to use the new ID-based actions so that internal service logic is consistent and efficient.
## Context
Following BEP-1039 (Image ID Based Service Logic Migration), new ById Actions have been added in BA-4097. This issue covers the gradual migration of existing canonical-based calls to use the new ID-based actions.
This is Stage 1 Phase 2 of the three-stage migration outlined in BEP-1039:
- Stage 1: Service Logic Migration (BA-4097 + this issue)
- Stage 2: ImageV2 Schema Addition (BEP-1038)
- Stage 3: API Migration (future)
## Scope
- Replace canonical-based Action calls with ById Action calls where applicable
- Update GraphQL resolvers (gql_legacy) to resolve image_id first, then use ById actions
- Migrate cache keys from canonical-based to ID-based
- Mark legacy Actions for deprecation
## Acceptance Criteria
- [ ] Existing image operations use ById Actions internally
- [ ] Cache keys unified to image_id basis
- [ ] Legacy Actions marked with deprecation notices
- [ ] No breaking changes to external API
## Related
- BEP-1039: Image ID Based Service Logic Migration
- BA-4097: Add Image ID-based service logic
- BEP-1038: ImageV2 GQL Implementation
JIRA Issue: BA-4130
Contributor guide
Assessment
This issue has not been assessed yet.