ezgh obs dashboards apply -f <file.json> [flags]Make a dashboard match a JSON file: { “name”, “description”, “tags”, “spec” }, with name and spec required. The dashboard is the one the file’s id or slug names (it must exist), else the one named name, if exactly one is. When there’s none, apply creates it.
An update replaces the spec whole, and sets the name, and the description and tags when the file has them (fields left out stay as they are). It’s sent with the ETag ezgh just read: if someone saves the dashboard in between, nothing changes, and ezgh says to run apply again. A change of name, description or spec saves a new version; a file that changes nothing saves none.
The file can be the output of ezgh obs dashboards get -o json: its other fields are ignored. Keep the file next to the service it describes, and apply it from CI.
Part of ezgh obs dashboards.
Examples
ezgh obs dashboards apply -f dashboards/checkout.json
ezgh obs dashboards get checkout -o json > checkout.json # edit, then:
ezgh obs dashboards apply -f checkout.jsonFlags
| Flag | Type | Default | Description |
|---|---|---|---|
-f, --file |
string | the dashboard’s JSON file, or - for stdin |
This command also takes the global flags.