staroid-python
Staroid python client library
Install
pip install staroid
Quickstart
from staroid import Staroid
star = Staroid()
# Create a ske kubernetes cluster
my_cluster = star.cluster().create("my cluster", "gcp us-west1")
# Launch a project
ns = star.namespace(my_cluster).create("my_app", "GITHUB/staroids/namespace:master")
# stop instance
ns = star.namespace(my_cluster).stop("my_app")
# restart instance
ns = star.namespace(my_cluster).start("my_app")
# delete instance
ns = star.namespace(my_cluster).delete("my_app")
Configuration
Environment variables
| Env variable | optional | description |
|---|---|---|
| STAROID_ACCESS_TOKEN | false | Access token generated from here |
| STAROID_ACCOUNT | true | Account to use. e.g. GITHUB/my_github_login |
Config file
Altanatively, you can create ~/.staroid/config.yaml file like below.
access_token: <your access token> # access token from https://staroid.com/settings/accesstokens
account: <account> # optional. e.g. "GITHUB/my_github_login"
When both config file and environment variables exist, environment variable will take precedence.
Metadata
Release files for staroid 0.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 | |
|---|---|---|---|---|
| staroid-0.1.0.tar.gz | 7.4 kB | Without provenance | Details |
Release files / staroid-0.1.0.tar.gz
| Download URL | staroid-0.1.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccbc730dca807e5c25e93007c50d9929c3b18e9c01c0f8820f131ef50b64d720
|
|
BLAKE2b-256 checksum How to use checksums |
4fc05e3d17348f34a835a3b22eb082b082dff2b7649b3a3bc5805cad1eb226f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.49.0 CPython/3.8.5
|
Security for staroid 0.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.