Vault
Vault has 6 operations in gum's generated catalog. Start with search when you know the task, use describe to inspect request fields and scopes, then dispatch through the command that matches the operation risk class.
| Count | Value |
|---|---|
| Family | Workspace administration |
| Operations | 6 |
| Risk classes | 1 destructive, 2 read, 3 write |
| Auth strategies | 6 byo_oauth |
Start here
gum search "vault"
gum describe vault.matters.get
gum read vault.matters.get --args '{"matterId":"<matterId>"}' --output jsonFor write-class operations, gum requires the write command and an explicit write gate:
gum describe vault.matters.close
gum write vault.matters.close --allow-write --args '{"matterId":"<matterId>"}'For destructive operations, run the call once for a confirmation envelope, review the target, then retry with the returned token:
gum destructive vault.matters.delete --args '{"matterId":"<matterId>"}'
gum destructive vault.matters.delete --args '{"matterId":"<matterId>"}' --confirmed --token '<confirmation_token>'Operations
| Operation | Risk | Auth | Summary |
|---|---|---|---|
vault.matters.close |
write |
byo_oauth |
Close an eDiscovery matter by matterId. |
vault.matters.create |
write |
byo_oauth |
Create a new eDiscovery matter (args.body: name, description). |
vault.matters.delete |
destructive |
byo_oauth |
Delete a matter by matterId (must be closed first). Destructive — requires confirmation per §6.1. |
vault.matters.get |
read |
byo_oauth |
Fetch a matter by matterId. |
vault.matters.list |
read |
byo_oauth |
List the eDiscovery matters the caller can access (state, view, pageSize). |
vault.matters.update |
write |
byo_oauth |
Update a matter's name/description by matterId. |
Next
- Use API workflows for search, describe, invoke, and error handling.
- Use Auth guides for service-specific Google setup.
- Use Command index for CLI flags and generated help.
