JiriOndrusek opened a new pull request, #6302: URL: https://github.com/apache/camel-quarkus/pull/6302
fixes https://github.com/apache/camel-quarkus/issues/4127 requires https://github.com/apache/camel/pull/14970 (I'm keeping this PR as draft, because the camel PR is not merged at this time and the CI should fail without it) - Strict validation of certificates for client is turned off, because it is not possible to customize the sslContext for the client - This PR introduces parent of splunkTest, whih allows to run test with scheme https or http - Bunch of splunk configuration was refacored - Certificate generation was added (keytool approch has to be used, because the *.pem files are concatenated in the *TestResource class) - Ppositive and negative tests for SSL are added <!-- Uncomment and fill this section if your PR is not trivial [ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #. [ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough. [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea. [ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request. [ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html --> -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
