[GitHub] azagrebin opened a new pull request #6967: [FLINK-10628][E2E][SSL] Enable mutual REST SSL auth in e2e tests

[GitBox <gi...@apache.org>]

azagrebin opened a new pull request #6967: [FLINK-10628][E2E][SSL] Enable mutual REST SSL auth in e2e tests
URL: https://github.com/apache/flink/pull/6967
 
 
   ## What is the purpose of the change
   
   This PR enables mutual SSL authentication in batch all around and streaming file sink end-to-end tests. It also splits deprecated ssl configs into separate SSL configuration for internal and external REST communication. The curl commands, which query Flink REST API, are fixed with relevant SSL args to check and provide certificates where needed.
   
   ## Brief change log
   
     - separate common_ssl.sh from common.sh
     - fix curls with SSL in common.sh which query Flink
     - enable mutual SSL authentication in test_batch_allround.sh and test_streaming_file_sink.sh
   
   ## Verifying this change
   
   build Flink and run:
   FLINK_DIR=./build-target ./flink-end-to-end-tests/run-single-test.sh ./flink-end-to-end-tests/test-scripts/test_batch_allround.sh
   FLINK_DIR=./build-target ./flink-end-to-end-tests/run-single-test.sh ./flink-end-to-end-tests/test-scripts/test_streaming_file_sink.sh
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services