# grizzly を Homebrew, Nix でインストール

grizzly のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。

## インストール

```sh
sudo av install brew:grizzly
```

追加のインストールコマンド:

### macOS

- Homebrew (100%):

```sh
brew install grizzly
```

  証拠: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#grizzly
```

  証拠: nixpkgs package indexes: pkgs/by-name/gr/grizzly/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## パッケージ情報

- **パッケージキー:** brew:grizzly
- **パッケージマネージャ:** Homebrew
- **バージョン:** 0.7.1
- **ソース概要:** Command-line tool for managing and automating Grafana dashboards
- **ホームページ:** <https://grafana.github.io/grizzly/>
- **リポジトリ:** <https://github.com/grafana-cold-storage/grizzly>
- **最終更新:** 2026-07-27T14:57:52+02:00
- **生成日時:** 2026-08-03T19:37:03+00:00

## 実行可能ファイル

- grr (エイリアス)

## インストール挙動

- Bottle: 利用不可

## バージョンと鮮度

- ページ生成日: 2026-08-03
- マネージャ版: 0.7.1
## プロジェクトの歴史と使われ方

Grafana Grizzly is a CLI for managing observability resources as code. It packages a GitOps-style Grafana workflow into the `grr` command, letting teams define dashboards, alerting, and recording rules in files and apply them to Grafana APIs.

### プロジェクトの歴史

Grizzly came out of the Grafana-as-code ecosystem, where dashboards and related resources moved from UI-only configuration into version-controlled JSON, Jsonnet, and Kubernetes-like YAML. The official repository describes it as a command-line tool for managing observability resources as code and building those updates into deployment pipelines.

Grafana's own as-code writing placed Grizzly beside Grafonnet, Terraform, and the Grafana Operator as one of the tools for publishing Git-based dashboard definitions. Later Grafana documentation marked Grizzly as deprecated and directed users toward Grafana CLI workflows.

### 採用の歴史

Grizzly appealed to teams that wanted dashboards and alerts reviewed in pull requests, pushed by CI, and kept near application code. Grafana blog posts used it as an example tool for dashboard-as-code workflows and for reviewing Git-based dashboards locally.

The package's adoption was strongest among Grafana and Jsonnet users who wanted a CLI bridge between rendered dashboard definitions and live Grafana instances.

### 使われ方

Users configure a context with Grafana connection details, then use `grr` commands to apply, get, diff, watch, or serve resources. The settings file can carry both target URLs and authentication material, which is why the package has the same path for configuration and credentials.

In package-manager culture it is a small operational binary: install it, point it at Grafana, and wire it into local dashboard development or CI.

### パッケージ好きにとっての重要性

Grizzly is interesting because it shows observability configuration moving into the same package and Git workflows as application code. It is not a dashboard renderer by itself; it is glue between source-controlled resource definitions and Grafana's APIs.

It also shows the lifecycle risk of cloud-infrastructure CLIs. A useful package can become a migration step when its owning platform standardizes around a replacement.

### タイムライン

- 2020: Grafana described Grizzly as a tool for managing observability resources with code.
- 2021: Users discussed Grizzly in CI workflows for generated Grafana dashboards.
- 2024: Grafana documented Grizzly in Git-based dashboard editing workflows.
- Afterward: Grafana documentation marked Grizzly as removed from active support and pointed users to Grafana CLI.

### Related projects

- Grafana is the observability platform Grizzly manages.
- Grafonnet and Jsonnet are common dashboard-as-code inputs used with Grizzly-style workflows.
- Grafana Terraform provider and Grafana Operator cover adjacent infrastructure-as-code workflows.
- grafanactl and Grafana CLI workflows are successors in Grafana's documented direction.

### ソース

- <https://github.com/grafana/grizzly>
- <https://grafana.com/blog/a-complete-guide-to-managing-grafana-as-code-tools-tips-and-tricks/>
- <https://grafana.com/blog/edit-your-git-based-grafana-dashboards-locally/>
- <https://grafana.com/docs/grafana/latest/as-code/infrastructure-as-code/grizzly/>
- <https://grafana.github.io/grizzly>


## セキュリティノート

narrow executable package without higher-risk signals.

- **Geiger リスク:** グリーン / 低
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Linux: $XDG_CONFIG_HOME/grizzly/settings.yaml, ~/.config/grizzly/settings.yaml
- macOS: ~/Library/Application Support/grizzly/settings.yaml
- Windows: %LOCALAPPDATA%\grizzly\settings.yaml

## Credential files

- Linux: $XDG_CONFIG_HOME/grizzly/settings.yaml, ~/.config/grizzly/settings.yaml
- macOS: ~/Library/Application Support/grizzly/settings.yaml
- Windows: %LOCALAPPDATA%\grizzly\settings.yaml
## 他のパッケージマネージャ記録

- Nix - grizzly: normalized package name match | nixpkgs package indexes: pkgs/by-name/gr/grizzly/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## 関連リンク

- [grizzly](https://pkg.so/ja/pkg/npm/grizzly/) - Same normalized package name exists in another local package ecosystem.

## Combined YAML source

View the package source record on GitHub. [combined/grizzly.yml](https://github.com/mxcl/pkgdb/blob/main/combined/grizzly.yml)


## ソース

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph