The Blameless SLO CLI supports the following commands to manage your [SLO resources](#the-blameless-slo-data-model) in your own Blameless instance. ```unix $ blameless-slo validate $ blameless-slo deploy $ blameless-slo delete ```
npm install @blamelesshq/blameless-sloThe Blameless SLO CLI supports the following commands to manage your SLO resources in your own Blameless instance.
``unix`
$ blameless-slo validate
$ blameless-slo deploy
$ blameless-slo delete
* Using the deploy command option, You can create and update multiple SLO resources at the same time by grouping your SLO YAML files under the same directory or one SLO resource (1 yaml file) at a time.
* As you develop your SLO specifications for your services, you can use the validate command option prior to deploying to your Blameless instance.
* If you need to remove your SLO resources from Blameless SLO Manager, you can use the delete command option.
* If you have an SLO resource refering to a resource which does not exist in your Blameless instance under SLO Manager (e.g. SLI --> Service or SLO --> User Journey), the Blameless SLO CLI will report the issue and it will not create the new SLO resource.
* Check the Naming resources section to make sure you are appropriately naming your resources before you create or update SLO resources in SLO Manager on your Blameless instance.
The Blameless SLO CLI is publicly available as an NPM package which can be installed as followed:
`unix`
$ npm install -g @blamelesshq/blameless-slo
> Contact Blameless Customer Success (cs@blameless.io) to obtain your Client ID and Client Secret which is associated to your Blameless instance:
The following environment variables must be set, before you can execute the blameless-slo command:`unix`
$ export BLAMELESS_OAUTH_CLIENT_ID=
$ export BLAMELESS_OAUTH_CLIENT_SECRET=
$ export BLAMELESS_OAUTH_AUDIENCE=
$ export BLAMELESS_TENANT_DOMAIN=
You will be reminded to set those environment variables if one or more of those have not been set:
`unix
$ blameless-slo
[BLAMELESS] ERROR : Config is missing. Please set correct config values via environment variables.
Required Env Vars:
BLAMELESS_OAUTH_CLIENT_ID
BLAMELESS_OAUTH_CLIENT_SECRET
BLAMELESS_OAUTH_AUDIENCE
BLAMELESS_TENANT_DOMAIN
`
The validate command is used to validate .yaml specs before deploying the defined SLO resources in Blameless SLO Manager.
`jsx`
blameless-slo validate -f
Options:
*
Examples:
`jsx`
blameless-slo validate -f sample1
There are tree types of validations messages:
- :heavy_check_mark: [BLAMELESS] SUCCESS
- :warning:
- :x:
Examples:
Example when the validation completed successfully for a selected YAML spec:
`bat`
blameless-slo validate -f ./specs/user_journey.yaml
:heavy_check_mark: [BLAMELESS] SUCCESS : ========== Blameless UserJourney Validated Successfully ==========.
Example when the option is incorrect (typo):
`bat`
blameless-slo validate -e ./specs/
error: required option '-f,--filePath
Example: Showing the list of syntax errors in the YAML spec
`bat`
blameless-slo validate -f ./specs/sli.yaml
:x: [BLAMELESS] ERROR : ========== Blameless SLI Validation Errors ==========.
[BLAMELESS] ERROR : 1: "spec.metricSource.mode" must be one of [direct, gcp, lambda]
[BLAMELESS] ERROR : 2: "spec.metricSource.sourceName" is required
[BLAMELESS] ERROR : 3: "spec.metricSource.name" is not allowed
The deploy command is used to create/update SLO resources in Blameless. When you execute that command, it first validates the specified yaml files, and if everything is okay, it will proceed further by deploying those resources.
* When multiple SLO resources are provided as input, the Blameless SLO CLI automatically makes sure to create resources in the following order in your Blamelesss instance: Service > SLI > User Journey > Error Budget > SLO.
* SLO resources are uniquely identified by the name provided in your SLO specification.
`jsx`
blameless-slo deploy -f
Options:
*
The delete command is used to delete SLO resources from Blameless SLO Manager. When you execute that command, it first validates the specified yaml files, and if everything is okay, it will proceed further by deleting those resources.
`jsx`
blameless-slo deploy -f
Options:
*
To view sample files for each type of resource check out our sample repo.