Snowflake-Smart-Suspend intelligently suspends the running warehouse which are not being used and reaching hour boundary. Currently designed for warehouses with auto-resume enabled and without auto-suspend for better optimisation.
Usage and Details
Installation:
pip install snowflake-smart-suspend
Typical usage often looks like this:
smart_suspend start -c connections -r <role which has access to warehouses of interest> -s 55 -i 30 -w <space separated list of warehouses>
You can find the details about all the options with:
smart_suspend -h smart_suspend --help
Configurations
If you have snowsql installed and running on the server smart-suspend will work out of the box If not you will have to have file at location HOME/.snowsql/config with snowflake cred:
[connections] accountname = <account name> username = <username> password = <password>
Logging
Logs could be find in /var/log/smartsuspend/system.log. You might need to adjust the permissions to log directory during installation.
Dependancies
Its written for Python3 which is the present and future of the language
Metadata
Release files for snowflake-smart-suspend 0.2.2
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 |
|---|---|---|---|---|
| snowflake-smart-suspend-0.2.2.tar.gz | 6.2 kB | Without provenance | Details for snowflake-smart-suspend-0.2.2.tar.gz |
Release files / snowflake-smart-suspend-0.2.2.tar.gz
| Download URL | snowflake-smart-suspend-0.2.2.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e7f7d6532d0b545e449ed54e29f57a75ab7e889e6e5288a29c9e65175588e79
|
|
BLAKE2b-256 checksum How to use checksums |
a5a1bab039268e9cdf0de9ffd579032f18c8220e0c809f3f0e04057bb536d729
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for snowflake-smart-suspend 0.2.2
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.