RANGER-5175:Functional Test Case Support for KMS API and HDFS Encryption#881
Open
ChinmayHegde24 wants to merge 1 commit intoapache:masterfrom
Open
RANGER-5175:Functional Test Case Support for KMS API and HDFS Encryption#881ChinmayHegde24 wants to merge 1 commit intoapache:masterfrom
ChinmayHegde24 wants to merge 1 commit intoapache:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pytest Functional Test-suite
This test suite validates REST API endpoints for KMS (Key Management Service) and tests HDFS encryption functionalities including key management and file operations within encryption zones.
hdfs : contains test cases for checking KMS functionality through hdfs encryption lifecycle
kms : contains test cases for checking KMS API functionality
Directory Structure
Running Tests
Container Setup
Before running the tests, configure container behaviour using the following environment variable:
After the initial setup, you can disable fresh container creation by setting below for the next re-runs:
Executing Tests
Run the test script using:
Note (Optional)
If you only need to start the infrastructure i.e containers (without running tests):
This is useful when tests are failing due to incomplete container setup.
After the infrastructure is successfully up, set RUN_TESTS=1 and rerun the script to execute the tests without setup issues.