refactor: make component label configurable #101
Merged
+1,832
−384
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
robertgraeff
approved these changes
Aug 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
With openmcp-project/service-provider-crossplane#11, there is the need to make the component label configureable, when using the
ObjectComponentandObjectReconcilerinterface. This PR makes it possible to pass the component label such ascore.orchestrate.cloud.sap/componentwhen initialising a newObjectReconciler. This change enables the service-provider-crossplane to better make use of thepkg/juggler/objectlibrary. The PR does not create any breaking changes, since logic just got refactored.Which issue(s) this PR fixes:
NONE
Special notes for your reviewer:
NONE
Release note: