base on A command line utility to work with Sentry. <p align="center"> <a href="https://sentry.io/?utm_source=github&utm_medium=logo" target="_blank"> <picture> <source srcset="https://sentry-brand.storage.googleapis.com/sentry-logo-white.png" media="(prefers-color-scheme: dark)" /> <source srcset="https://sentry-brand.storage.googleapis.com/sentry-logo-black.png" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" /> <img src="https://sentry-brand.storage.googleapis.com/sentry-logo-black.png" alt="Sentry" width="280"> </picture> </a> </p> # Official Sentry Command Line Interface [](https://github.com/getsentry/sentry-cli/actions?query=workflow%3ACI) [](https://github.com/getsentry/sentry-cli/releases/latest) [](https://www.npmjs.com/package/@sentry/cli) [](https://github.com/getsentry/sentry-cli/blob/master/LICENSE) This is a Sentry command line client for some generic tasks. Right now this is primarily used to upload debug symbols to Sentry if you are not using the Fastlane tools. * Downloads can be found under [Releases](https://github.com/getsentry/sentry-cli/releases/) * Documentation can be found [here](https://docs.sentry.io/hosted/learn/cli/) ## Installation If you are on OS X or Linux, you can use the automated downloader which will fetch the latest release version for you and install it: curl -sL https://sentry.io/get-cli/ | bash We do, however, encourage you to pin the specific version of the CLI, so your builds are always reproducible. To do that, you can use the exact same method, with an additional version specifier: curl -sL https://sentry.io/get-cli/ | SENTRY_CLI_VERSION=2.33.1 bash This will automatically download the correct version of `sentry-cli` for your operating system and install it. If necessary, it will prompt for your admin password for `sudo`. For a different installation location or for systems without `sudo` (like Windows), you can `export INSTALL_DIR=/custom/installation/path` before running this command. If you are using `sentry-cli` on Windows environments, [Microsoft Visual C++ Redistributable](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist) is required. To verify it’s installed correctly you can bring up the help: sentry-cli --help ### pip _New in 2.14.3_: `sentry-cli` can also be installed using `pip`: ```bash pip install sentry-cli ``` ### Node Additionally, you can also install this binary via npm: npm install @sentry/cli When installing globally, make sure to have set [correct permissions on the global node_modules directory](https://docs.npmjs.com/getting-started/fixing-npm-permissions). If this is not possible in your environment or still produces an EACCESS error, install as root: sudo npm install -g @sentry/cli --unsafe-perm By default, this package will download sentry-cli from the CDN managed by [Fastly](https://www.fastly.com/). To use a custom CDN, set the npm config property `sentrycli_cdnurl`. The downloader will append `"/<version>/sentry-cli-<dist>"`. ```sh npm install @sentry/cli --sentrycli_cdnurl=https://mymirror.local/path ``` Or add property into your `.npmrc` file (https://www.npmjs.org/doc/files/npmrc.html) ```rc sentrycli_cdnurl=https://mymirror.local/path ``` There are a few environment variables that you can provide to control the npm installation: ``` SENTRYCLI_CDNURL=<url> # Use alternative cdn url for downloading binary SENTRYCLI_USE_LOCAL=1 # Use local instance of sentry-cli binary (looked up via $PATH environment) SENTRYCLI_SKIP_DOWNLOAD=1 # Skip downloading binary entirely SENTRYCLI_NO_PROGRESS_BAR=1 # Do not print the progress bar when downloading binary (default for non-TTY environments like CI) SENTRYCLI_LOG_STREAM=<stdout|stderr> # Changes where to redirect install script output ``` When using `sentry-cli` via JavaScript API or any 3rd party plugin that is consuming said API, you can also use `SENTRY_BINARY_PATH=<path>` alongside `SENTRYCLI_SKIP_DOWNLOAD=1` to completely control what binaries are downloaded and used throughout the whole process. If you're installing the CLI with NPM from behind a proxy, the install script will use either NPM's configured HTTPS proxy server or the value from your `HTTPS_PROXY` environment variable. ### Homebrew A homebrew recipe is provided in the `getsentry/tools` tap: brew install getsentry/tools/sentry-cli ### Docker As of version _1.25.0_, there is an official Docker image that comes with `sentry-cli` preinstalled. If you prefer a specific version, specify it as tag. The latest development version is published under the `edge` tag. In production, we recommend you to use the `latest` tag. To use it, run: ```sh docker pull getsentry/sentry-cli docker run --rm -v $(pwd):/work getsentry/sentry-cli --help ``` Starting version _`2.8.0`_, in case you see `"error: config value 'safe.directory' was not found;"` message, you also need to correctly set UID and GID of mounted volumes like so: ```sh docker run --rm -u "$(id -u):$(id -g)" -v $(pwd):/work getsentry/sentry-cli --help ``` This is required due to security issue in older `git` implementations. See [here](https://github.blog/2022-04-12-git-security-vulnerability-announced/) for more details. ## Update To update sentry-cli to the latest version run: ```sh sentry-cli update ``` ## Compiling In case you want to compile this yourself, you need to install at minimum the following dependencies: * Rust stable and Cargo * Make, CMake and a C compiler Use cargo to compile: $ cargo build Also, there is a Dockerfile that builds an Alpine-based Docker image with `sentry-cli` in the PATH. To build and use it, run: ```sh docker build -t sentry-cli . docker run --rm -v $(pwd):/work sentry-cli --help ``` ", Assign "at most 3 tags" to the expected json: {"id":"9797","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"