-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Expand file tree
/
Copy pathcoder_support_bundle_--help.golden
More file actions
38 lines (28 loc) · 1.47 KB
/
coder_support_bundle_--help.golden
File metadata and controls
38 lines (28 loc) · 1.47 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
coder v0.0.0-devel
USAGE:
coder support bundle [flags] <workspace> [<agent>]
Generate a support bundle to troubleshoot issues connecting to a workspace.
This command generates a file containing detailed troubleshooting information
about the Coder deployment and workspace connections. You must specify a
single workspace (and optionally an agent name).
OPTIONS:
-O, --output-file string, $CODER_SUPPORT_BUNDLE_OUTPUT_FILE
File path for writing the generated support bundle. Defaults to
coder-support-$(date +%s).zip.
--pprof bool, $CODER_SUPPORT_BUNDLE_PPROF
Collect pprof profiling data from the Coder server and agent. Requires
Coder server version 2.28.0 or newer.
--template string, $CODER_SUPPORT_BUNDLE_TEMPLATE
Template name to include in the support bundle. Use
org_name/template_name if template name is reused across multiple
organizations.
--url-override string, $CODER_SUPPORT_BUNDLE_URL_OVERRIDE
Override the URL to your Coder deployment. This may be useful, for
example, if you need to troubleshoot a specific Coder replica.
--workspaces-total-cap int, $CODER_SUPPORT_BUNDLE_WORKSPACES_TOTAL_CAP
Maximum number of workspaces to include in the support bundle. Set to
0 or negative value to disable the cap. Defaults to 10.
-y, --yes bool
Bypass confirmation prompts.
———
Run `coder --help` for a list of global options.