operator-framework / operator-framework/java-operator-sdk
Consider removing `Cloner` interface
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 944
- Forks
- 242
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 43
Description
Changes in generic matcher and updater open up the possibility that resources being cloned via the configured Cloner might be serialized differently after being processed by the generic updater. While this is probably a low probably event, it might be better to remove the possibility to customize the cloner (though that would also remove potential optimization options, I'm not sure that anyone is currently doing this or even is aware that is a possibility 😁)
Originally posted by @metacosm in https://github.com/operator-framework/java-operator-sdk/pull/2014#discussion_r1302682685
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by tracing the configured Cloner through the generic matcher and updater, then examine how cloning and serialization interact after updates. Done means establishing whether the customizable Cloner should be removed, including the effect on possible optimization options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100