|
| 1 | +``` |
| 2 | +$ sentry-cli proguard upload --help |
| 3 | +? success |
| 4 | +Upload ProGuard mapping files to a project. |
| 5 | + |
| 6 | +Usage: sentry-cli[EXE] proguard upload [OPTIONS] [PATH]... |
| 7 | + |
| 8 | +Arguments: |
| 9 | + [PATH]... The path to the mapping files. |
| 10 | + |
| 11 | +Options: |
| 12 | + -o, --org <ORG> The organization ID or slug. |
| 13 | + --header <KEY:VALUE> Custom headers that should be attached to all requests |
| 14 | + in key:value format. |
| 15 | + -p, --project <PROJECT> The project ID or slug. |
| 16 | + --auth-token <AUTH_TOKEN> Use the given Sentry auth token. |
| 17 | + --no-upload Disable the actual upload. |
| 18 | + This runs all steps for the processing but does not trigger the |
| 19 | + upload. This is useful if you just want to verify the mapping |
| 20 | + files and write the proguard UUIDs into a properties file. |
| 21 | + --log-level <LOG_LEVEL> Set the log output verbosity. [possible values: trace, debug, info, |
| 22 | + warn, error] |
| 23 | + --write-properties <PATH> Write the UUIDs for the processed mapping files into the given |
| 24 | + properties file. |
| 25 | + --quiet Do not print any output while preserving correct exit code. This |
| 26 | + flag is currently implemented only for selected subcommands. |
| 27 | + [aliases: --silent] |
| 28 | + --require-one Requires at least one file to upload or the command will error. |
| 29 | + -u, --uuid <UUID> Explicitly override the UUID of the mapping file with another one. |
| 30 | + This should be used with caution as it means that you can upload |
| 31 | + multiple mapping files if you don't take care. This however can be |
| 32 | + useful if you have a build process in which you need to know the |
| 33 | + UUID of the proguard file before it was created. If you upload a |
| 34 | + file with a forced UUID you can only upload a single proguard file. |
| 35 | + -h, --help Print help |
| 36 | + |
| 37 | +``` |
0 commit comments