Skip to main content

Welcome to the Split CLI 👋


NOTE: 9/24/2021 - A few months ago Split Skunkworks (aka developer advocacy) embarked on an experiment to create a command line interface (CLI) tool to provision and interact with Split accounts. The experiment was a success and we are now assessing putting formal engineering muscle behind it. For now, we are taking it offline until such time as we are ready to release a fully supported version.


The Split CLI is a Command Line Interface built to simplify onboarding, and make it easy to manage your entire feature flag lifecycle. The changes and updates you make to your splits through the CLI will be reflected immediately in the Split UI.


Throughout the CLI, to select an option, press the Enter/Return button on your keyboard unless otherwise noted.

🏠 Split Homepage

📚 Split Docs

Getting Started

Note: Python >=3.6 is required to use the CLI

pip install splitcli
splitcli

New Split Users

Upon running splitcli, the CLI will ask you if you have an existing account. Users who are new to Split should select the first option No, I need to create an account to create an account. You will be prompted to enter your first name, last name, email address, and phone number. You will then recieve a 6 digit one time password to authenticate.

Existing Split Users

If you have a Split account already, select Yes, take me to sign in from the initial prompt. You will then enter your email address, followed by your Admin API Key, which can be found in the Admin Settings of your Split profile. For more information on finding your Admin API Key, follow the directions here.

Main Menu

Manage Splits

A split is another name for a feature flag, which allows you to separate code deployment from feature release. When you select Manage Splits from the Main Menu, you will see a list of the splits that are already in your organization, as well as the option to create a new split.

To create a new split, select Create a new split from the menu. You will then be prompted to enter a name for your split, as well as a description. Next, you will choose whether you want a simple rollout, which will give you the ability to turn a feature on or off in any environment, or a custom rollout, where you can have a custom set of treatments.

You will then choose which environment you wish to manage your split in.

Show Full Definition JSON

Selecting this option will output the full JSON configuration of your split into your terminal.

Target Keys

Selecting this option will allow you to target users into your feature flag. You will select which treatment you are targeting, then add the users.

Target Segments

Selecting this option will allow you to target a segmented user goup to your feature flag. First select which treatment you are targeting, then select the segments you wish to target by pressing the space bar.

Ramp Split

Ramp split allows you to ramp up your split to a specific percentage of users. After selecting this option, you will be prompted to enter percentage of the userbase you wish to be in the ON treatment.

Kill Split

Killing a split turns the feature off in the environment you select. To kill a split, navigate to the split, and select Kill from the menu.

Restore Split

Restoring a split turns the split back on after it was killed. Your previous configurations for the Split will still be in place. To restore your split after it has been killed, select Restore from the menu.

Delete Definition

Deleting a split's definition will remove all targeting rules from the split. To delete a split's definition, select Delete definition from the menu.

Delete Split

Once your Split has met its definition of done, it can be deleted. To delete a split, select Delete split from the menu. This will delete the split in all environments.

Manage Segments

Segments are groups of users that you can use to target in your feature flags. When you select Manage Segments from the Main Menu, you will see a list of the segments that are already in your organization, as well as the option to create a new segment.

To create a new segment, select Create a new segment from the menu. You will then be prompted to enter a name, and description for that segmented user group. Once that segment is created, you will see it listed in the Manage Segments menu. Select the segment you created, and choose which environment you wish to manage it in. Here is where we will soon be adding key management capabilities, stay tuned!

To delete a segment, navigate into the segment you wish to delete, and select Delete segment.

Log Out

Selecting Log Out will log you out of the CLI.

Exit

Selecting Exit will exit out of the CLI.

Authors

👤 Talia Nassi

👤 Henry Jewkes

👤 Micah Silverman

Show your support

Give a ⭐️ if this project helped you!

Metadata

Release files for splitcli 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for splitcli 0.2.0
File Size Uploaded Provenance
splitcli-0.2.0.tar.gz 28.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for splitcli 0.2.0
File Interpreter ABI Platform
splitcli-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 61.6 kB

Release files / splitcli-0.2.0.tar.gz

Download URL splitcli-0.2.0.tar.gz
Size 28.0 kB
Tags Source
SHA-256 checksum
How to use checksums
e0669a645929b192cbeae46440bb56b376d508286a53e673430938b8049690f6
BLAKE2b-256 checksum
How to use checksums
f51128fcce57740f4302c23a822d6ffe7ef4e6b184daacb0f64676b093328e39
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/57.0.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.6

Release files / splitcli-0.2.0-py3-none-any.whl

Download URL splitcli-0.2.0-py3-none-any.whl
Size 33.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
68c2fa7297465bc8c2a786405a83ee87a3738dd7134abc76279692741ae35cc2
BLAKE2b-256 checksum
How to use checksums
813301b7fbb0635429c1d721db64b9e517165f143747f4e72c0aeef44a17d815
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/57.0.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.6

Security for splitcli 0.2.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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page