phantomjinx commented on issue #3667: URL: https://github.com/apache/camel-k/issues/3667#issuecomment-1260636823
> I don't think so. For upstream global e2e testing, `KamelInstallWithOperatorID()` also omits the operator ID so the IntegrationPlatform should be always `camel-k`: https://github.com/apache/camel-k/blob/main/e2e/support/test_support.go#L246 This is my bad explanation. We both agree on the issue that the IntegrationPlatform is named `camel-k` but the test calling `kamel run ... -x camel-k-kamelet ...` means the command searches for an IntegrationPlatform named `camel-k-kamelet` - see [here](https://github.com/apache/camel-k/blob/main/pkg/cmd/kamelet_add_repo.go#L85). Therefore, I think question 2, above needs to be considered: - Should the `add-repo` function: -- detect the installed IntegrationPlatform and compare operator ID. If they don't match, error out; -- attempt to find an IntegrationPlatform in ANY namespace with the given operatorID; -- drop the operatorID in the lookup of the IntegrationPlatform ([L85](https://github.com/apache/camel-k/blob/main/pkg/cmd/kamelet_add_repo.go#L85) above) I am not sure that fixing the test is a way to mitigate this problem. -- 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
