hernanDatgDev opened a new pull request, #4987:
URL: https://github.com/apache/camel-k/pull/4987

   <!-- Description -->
   Originally the operator determines that a native kit matches(is suitable 
for) an integration if
   
   - The number of sources for both integration and kit are equal
   - The content of the sources must match exactly.
   
   This is a problem for native builds where some languages are not required to 
be in kits such as xml. As a result an integration may have generated xml 
sources (like when adding an OpenAPI spec) which the kit simply would never 
have. My modification is to change `number of sources for both integration and 
kit are equal` to `the number of kit sources should not be greater than 
integration sources`. This is because the number of sources might not be equal 
and in fact could be less (as I've just described). Also the kit should not 
include additional sources not defined within the integration so the number of 
kit sources should not be more than the number of integrations sources.
   
   As for checking the second bullet, `The content of the sources must match 
exactly` I've included a language settings lookup before comparing the content 
of the sources. If the language settings for the source contain 
`sources-required-at-build-time==false` then those sources will of course not 
be in the kit so the content equality check can simply be skipped. Once skipped 
the kit retains its chance at being valid for the integration.
   
   <!--
   Enter your extended release note in the below block. If the PR requires
   additional action from users switching to the new release, include the string
   "action required". If no release note is required, write "NONE". 
   
   You can (optionally) mark this PR with labels "kind/bug" or "kind/feature" 
to make sure
   the text is added to the right section of the release notes. 
   -->
   
   **Release Note**
   ```release-note
   NONE
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to