greatsky-internal-metaflow
CLI for authenticating with the GreatSky Metaflow platform.
Install
# pip (use a venv)
pip install greatsky-internal-metaflow
# or with uv
uv pip install greatsky-internal-metaflow
Quick Start
# Authenticate (opens GitHub in your browser)
gsm login
# Verify everything is working
gsm validate
# Run Metaflow flows — no further config needed
python my_flow.py run
Commands
Authentication
| Command | Description |
|---|---|
gsm login [--scope global|project|venv] |
Authenticate via GitHub Device Flow |
gsm use-key <key> |
Configure using a service key (no browser needed) |
gsm logout |
Remove local credentials and config |
gsm status |
Show current authentication state |
gsm validate |
Check auth and platform connectivity |
gsm refresh |
Force re-fetch platform config from the auth API |
gsm revoke |
Immediately revoke your current API key |
gsm cleanup |
Remove legacy config files from before per-env scoping |
Service Keys
| Command | Description |
|---|---|
gsm service-key create <label> [--ttl 30d] |
Create a service key for programmatic access |
gsm service-key list |
List your active service keys |
gsm service-key revoke <label> |
Revoke a service key |
Admin (org members only)
| Command | Description |
|---|---|
gsm admin invite <user> [--expires 90d] |
Invite a GitHub user as guest |
gsm admin revoke <user> |
Remove a guest's access |
gsm admin revoke-keys <user> |
Revoke all API keys for a user |
gsm admin guests |
List all invited guests |
gsm admin list-service-keys |
List all service keys across all users |
gsm admin revoke-service-key --user <user> --label <label> |
Revoke a specific user's service key |
Hugging Face Integration
The package includes first-class Hugging Face Hub support. When running on the
platform, HF_TOKEN and HF_ORG are injected automatically -- no manual setup.
All dataset/model names without a / are auto-prefixed with the org (Great-Sky/).
Datasets
from greatsky_internal_metaflow.hf import load_dataset, save_dataset, list_datasets
# Load a dataset with version tracking (org prefix auto-resolved)
ds, version = load_dataset("my-dataset", split="train")
self.dataset_version = version # store as Metaflow artifact for lineage
# Save a dataset (accepts Dataset, DataFrame, dict, or directory path)
version = save_dataset(my_dataframe, "my-processed-dataset")
version = save_dataset({"text": texts, "label": labels}, "my-dataset")
version = save_dataset(hf_dataset, "my-dataset", commit_message="v2 cleaned")
# List all org datasets
for ds_info in list_datasets():
print(ds_info["id"], ds_info["downloads"])
The DatasetVersion object captures the exact HF commit SHA, split, timestamp,
and Metaflow run context. Query it later via the Metaflow Client API:
from metaflow import Flow
run = Flow("HFTrainingFlow").latest_run
print(run.data.dataset_version)
# DatasetVersion(Great-Sky/imdb@a3b5c8d2, split=train, run=HFTrainingFlow/42)
Models
from greatsky_internal_metaflow.hf import push_model_to_hub, pull_from_hub, sync_s3_to_hf
# Pull a model (org prefix auto-resolved)
local_path = pull_from_hub("my-model")
# Push a trained model to Great-Sky/my-model-finetuned
url = push_model_to_hub("/tmp/output", "my-model-finetuned")
# S3 <-> HF bridge
sync_s3_to_hf("s3://bucket/models/my-model", "my-model")
With metaflow-checkpoint decorators
Install with the [metaflow] extra to get @huggingface_hub, @model, and
@checkpoint decorators:
pip install "greatsky-internal-metaflow[metaflow]"
# or: uv pip install "greatsky-internal-metaflow[metaflow]"
from metaflow import FlowSpec, step
from metaflow_extensions.obcheckpoint.plugins.hf_hub_decorator import huggingface_hub
class MyFlow(FlowSpec):
@huggingface_hub(models=["distilbert-base-uncased"])
@step
def train(self):
...
Locally
If running outside the platform, set HF_TOKEN and HF_ORG as environment
variables, or authenticate with huggingface-cli login.
How It Works
gsm loginstarts a GitHub Device Flow — you get a code to enter at github.com/login/device- Once authorized, the CLI exchanges the GitHub token with the GreatSky auth API for a platform API key
- The API key and Metaflow config are written to a
.greatsky_gsm/directory (project, venv, or global scope) - The Metaflow extension reads that config automatically — no wrappers or env vars needed
API keys are valid for 14 days and are automatically revoked if you leave the GitHub org.
Config Resolution
The CLI resolves config from three locations, in priority order:
- Project —
.greatsky_gsm/in the nearest directory containingpyproject.tomlorsetup.py - Virtualenv —
.greatsky_gsm/inside$VIRTUAL_ENV - Global —
~/.greatsky_gsm/
Use --scope with gsm login to control where credentials are stored.
Development
git clone https://github.com/greatsky-ai/greatsky-internal-metaflow.git
cd greatsky-internal-metaflow
uv venv && uv pip install -e ".[dev]"
uv run pytest
uv run ruff check src/ tests/
Versioning
Versions are derived automatically from git tags via hatch-vcs. To release:
git tag v0.2.0
git push origin v0.2.0
The publish workflow runs lint, tests, and smoke tests before pushing to PyPI.
Metadata
Release files for greatsky-internal-metaflow 0.1.14
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 |
|---|---|---|---|---|
| greatsky_internal_metaflow-0.1.14.tar.gz | 193.3 kB | With provenance | Details for greatsky_internal_metaflow-0.1.14.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| greatsky_internal_metaflow-0.1.14-py3-none-any.whl | Python 3 | none | any | Details for greatsky_internal_metaflow-0.1.14-py3-none-any.whl |
Total release size: 223.2 kB
Release files / greatsky_internal_metaflow-0.1.14.tar.gz
| Download URL | greatsky_internal_metaflow-0.1.14.tar.gz |
|---|---|
| Size | 193.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f080f3d1c19cc2f4c46ef6e696ad1244d03ce6d3e1095fafbdf16220f411e3b
|
|
BLAKE2b-256 checksum How to use checksums |
d7778559361f5c1a4528435b4819d27306ce57f8164513bd74a6e374caf8b19b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 2, 2026.
Transparency logRelease files / greatsky_internal_metaflow-0.1.14-py3-none-any.whl
| Download URL | greatsky_internal_metaflow-0.1.14-py3-none-any.whl |
|---|---|
| Size | 29.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e892b4aae7f4dad074b8dfacf8307cc652384370ab48f464ac2dc164abe5269
|
|
BLAKE2b-256 checksum How to use checksums |
a3bb9c418484d004d328a44a36fceb3d32be3e0103786786646c74d89494c269
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 2, 2026.
Transparency logSecurity for greatsky-internal-metaflow 0.1.14
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for greatsky_internal_metaflow-0.1.14.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 2, 2026.
Transparency logA 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.