Skip to content

docs: improve javadoc for ResourceOperation on resource cloning and matching - #3502

Merged
csviri merged 1 commit into
operator-framework:mainfrom
csviri:matching-note
Jul 16, 2026
Merged

docs: improve javadoc for ResourceOperation on resource cloning and matching#3502
csviri merged 1 commit into
operator-framework:mainfrom
csviri:matching-note

Conversation

@csviri

@csviri csviri commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

Add java doc remark that the desired resource has to be clone (or fresh instance created)
in order to have the maching work correctly

Signed-off-by: Attila Mészáros a_meszaros@apple.com

…atching

Add java doc remark that the desired resource has to be clone (or fresh instance created)
in order to have the maching work correctly

Signed-off-by: Attila Mészáros <a_meszaros@apple.com>
Copilot AI review requested due to automatic review settings July 16, 2026 12:44
@openshift-ci
openshift-ci Bot requested review from metacosm and xstefank July 16, 2026 12:44

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the public Javadoc on ResourceOperations to clarify how matching behaves when comparing desired vs. actual resources, especially when the actual resource comes from an informer cache.

Changes:

  • Adds a new Javadoc note about matching secondary resources read from cache and the implications of cloning.
  • References ConfigurationService#cloneSecondaryResourcesWhenGettingFromCache() as a mitigation for cache-mutation risks.

@csviri
csviri merged commit 03ebfc7 into operator-framework:main Jul 16, 2026
53 of 67 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants