Check if the fragment doesnot already have a name#2825
Check if the fragment doesnot already have a name#2825amihalfa wants to merge 2 commits intoeclipse-jkube:masterfrom
Conversation
Eclipse JKube CI ReportStarted new GH workflow run for #2825 (2024-03-15T16:28:55Z) ⚙️ JKube E2E Tests (8298951289)
|
|
@amihalfa Welcome, Thanks a lot for contributing to Eclipse JKube 👍, In order to contribute to Eclipse, you would need to create an Eclipse Account and Sign Eclipse Contributor Agreement. Once you've created an eclipse account you would need to update your commit message with a |
|
@amihalfa : Could you please add a unit test for this too? |
04e48b5 to
50f3cc5
Compare
Signed-off-by: amihalfa <amirouche.halfaoui@rakuten.com>
50f3cc5 to
fdec19c
Compare
|
@rohanKanojia To be honest, I don't know what to do for the integration test |
|
Deployment and Service get created with opinionated defaults before invoking NameEnricher, Maybe we can modify NameEnricher to use this value to differentiate whether the name inside the current resource is opinionated (generated by plugin) or is actually set by the user? |
|
Polite ping, is this being worked on? |
|
Let me pick this up and discuss internally with the team about what needs to be done |
Description
In the
NamingEnricher, instead of overriding all the object names by the${jkube.enricher.jkube-name.name}, only overrides name to every object which misses a name.Fixes #2823
Type of change
test, version modification, documentation, etc.)