vdk-heartbeat 0.4.371920615

Versatile Data Kit Heartbeat and Health Test

Versatile Data Kit Heartbeat tool

Heartbeat tool for verifying deployed SDK and Control Service are functional and working correctly.
It checks that a job can be created, deployed, run and deleted.

• Health monitoring - one can schedule this run every few minutes and get heartbeat of their installation
• Regression testing after change in Versatile Data Kit, as clients would be able to customize vdk, they should have a way to check for regressions.
• Installation/Upgrade of VDK Control Service acceptance test.

What it does ?

It simulates Data Engineer workflow:

• Creates a data job, downloads keytab
• Deploys the data job with pre-defined scripts to run on a scheduled basis (every minute)
• Different data jobs and run tests can be run depending on the configuration.
  • This way it can be run in different modes. See config.py and the DATAJOB_DIRECTORY_* and JOB_RUN_TEST_* configuration options.
• Undeploys and deletes the data job.

Prerequisites

See heartbeat_config_example.ini and complete the TODOs inside

Installation

# TODO: Change to public PYPI index
pip install -i https://test.pypi.org/simple/ vdk-heartbeat

Configuration

See config.py for details on what can be configured.

Running

You can run the test locally, part of your CICD or schedule it to run periodically.

The test is passed or fail test.
If it fails it returns non-zero error code and prints the error.
It also produces a tests.xml file in junit xml format.

• Specify configuration in environment variables or in a file (use the file for things that can be in source control)
• Example:

export DATABASE_PASS=xxx
vdk-heartbeat -f heartbeat_config.ini

Extensibility

Users can replace the data job being deployed and executed and the run test which is used to verify the job run/execution.

See config.py DATAJOB_DIRECTORY_* and JOB_RUN_TEST_* configuration options.

Build, test, and release

See or run cicd/build.sh to build and test the project locally.

Release

Releases are made to PyPI.
Versioning follows https://semver.org.

• A release step in Gitlab CI is automatically triggered after merging changes if build/tests are successful.
• Update major or minor version when necessary only.