Cleanup: Store projected GVR/GVK in PublishedResource status

Open
#128 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
api, backend

Research direction

Start with the apiresourceschema controller and trace how projection currently obtains resources for PublishedResource processing. Done means the PublishedResource status stores the projected GVR and GVK for the primary resource and all related resources, so other controllers can reuse those values.

Written by the indexing model from the issue text.

Description

Right now, multiple controllers need to perform the Projection to get the resources they need to process in kcp. Since projection is a relatively involved process, it would be good if the agent simply stored these values in the status of a PublishedResource.

It should store the GVR for the primary resource and all related resources. The apiresourceschema controller is probably the best location to do that.

Dominant language
Go
Stars
25
Forks
30
Avg merge
3d 9h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kcp-dev/api-syncagent

All issues in kcp-dev/api-syncagent

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.