Reva CLI
The Reva CLI is used to manage Lendsmart deployment from the command line.
The primary intent is:
- mirror prod and QA
- make the deploys smooth with no manual intervention.
Overview
The goals of this project is to make deployments more flexible, and make the deployments faster.
Installation
pip install lendmart_reva
Configuration
Step 1: export
# Here the home is the root user home directory
export LENDSMART_REVA_HOME=$HOME (or)
# Here the home is the directory `/home/makesh`
export LENDSMART_REVA_HOME="/home/makesh"
# Here the ui home is the path to where the code of ui exists
export LENDSMART_REVA_UI_HOME='/home/makesh/ui'
# Here the ui home is the path to where the code of worklet exists
export LENDSMART_REVA_WORKLET_HOME="/home/makesh/worklet"
Step 3: mkdir reva
cd $LENDSMART_REVA_HOME
mkdir $LENDSMART_REVA_HOME/reva
Step 3: reva.conf
Copy the conf file to location $LENDSMART_REVA_HOME/reva/config.json
{
"dev": {
"api_root": "https://devapi.lendsmart.ai/api/v1",
"application_graphql_endpoint": "https://devappgraphql.lendsmart.ai/v1/graphql",
"application_graphql_auth_token": "",
"lendsmart_access_token": "<dev-lendsmart-access-token>"
},
"uat": {
"api_root": "https://testapi.lendsmart.ai/api/v1",
"application_graphql_endpoint": "https://devappgraphql.lendsmart.ai/v1/graphql",
"application_graphql_auth_token": "",
"lendsmart_access_token": "<dev-lendsmart-access-token>"
},
"prod": {
"api_root": "https://apiprod.lendsmart.ai/api/v1",
"application_graphql_endpoint": "https://devappgraphql.lendsmart.ai/v1/graphql",
"application_graphql_auth_token": "",
"lendsmart_access_token": "<prod-lendsmart-access-token>"
}
}
💁 Please update the aut_token, namespace and lendsmart_access_token for the appropriate environments. This is purposefully left out for security reasons.
Command Topics
reva namespaces- manage namespaces on Lendsmartreva workflows- manage workflow configurationreva loanproducts- manage loanproducts configurationreva sitesettings- manage sitesettings configurationreva worklet- manage worklet configuration
References
Metadata
Release files for lendsmart-reva 2.15
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 |
|---|---|---|---|---|
| lendsmart_reva-2.15.tar.gz | 31.1 kB | Without provenance | Details for lendsmart_reva-2.15.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lendsmart_reva-2.15-py3-none-any.whl | Python 3 | none | any | Details for lendsmart_reva-2.15-py3-none-any.whl |
Total release size: 89.6 kB
Release files / lendsmart_reva-2.15.tar.gz
| Download URL | lendsmart_reva-2.15.tar.gz |
|---|---|
| Size | 31.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8af7a6ea7264ba1ccfab1d4d7d58eb9307024523894e90d5504b7c39a2d733b0
|
|
BLAKE2b-256 checksum How to use checksums |
6db522b7d36b2d949f31e07fac8bac3104b624a39e7a22fdfded6e0a2df16f82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.6
|
Release files / lendsmart_reva-2.15-py3-none-any.whl
| Download URL | lendsmart_reva-2.15-py3-none-any.whl |
|---|---|
| Size | 58.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a5956456655494ff81518f003f5a76f690ba20f9fffc1d1c64c499bbb2f6506
|
|
BLAKE2b-256 checksum How to use checksums |
f7111d0025248129f5c45107f0911b837fc4797207682ffc3ba4991508b18404
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.6
|
Security for lendsmart-reva 2.15
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.