1.0.7 version para desplegar legacy
Oozie workflow tools AKA Slippin Jimmy
Generating Oozie workflows can be a tedious task, coding XML is not awesome, so you can generate them from Jinja templates using the process_templates.py script.
Installing the module
# pip install slippinj
About the dependencies, cx_Oracle is a Python extension module that enables Slippin Jimmy Scribe access to Oracle Database. This module is currently built against Oracle Client 11.2, 12.1 and 12.2, and is required for its operation to install the Oracle Instanclient. You can see how to install it at: http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html or https://anaconda.org/anaconda/oracle-instantclient for conda enviroment users.
Running the script
The arguments not provided and mandatory are asked for during script execution:
jimmy -h
Running the tests
Remember to remove the package before running the tests or the installed version will be used to run them
$ make test
Components of the module
Slippin Jimmy is composed by the above components: * Scribe: It creates the documentation and basic configuration from the Source database * Valet: It provisions the cluster with the needed software * Tlacuilo: It compiles the XML workflows from the YAML configuration * Anabasii: It uploads the code to the cluster * Cooper: Once the code has been uploaded it run the workflows * Hersir: Execute compilation, upload and once is uploaded the code to the cluster run the workflows
alt tag
Metadata
Release files for slippinj 3.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| slippinj-3.1.0.tar.gz | 24.2 kB | Without provenance | Details for slippinj-3.1.0.tar.gz |
Release files / slippinj-3.1.0.tar.gz
| Download URL | slippinj-3.1.0.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1329a3c87f6cf5c6b947d526275e13f8932ea5bfb4728ff34366e14ab40c415e
|
|
BLAKE2b-256 checksum How to use checksums |
f7ec793ed7216726cce4ebec3b801af671c25d5bfde4ddfc3e440c70c64191b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for slippinj 3.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.