This command modifies a support bundle.
Usage
supportbundle modify --id ID
[--prefix PREFIX]
[--send-now|--no-send-now]
[--delete-after-send|--no-delete-after-send]
[--upload-via-vms|--no-upload-via-vms]
[--access-key KEY]
[--secret-key KEY]
[--bucket-name NAME]
[--bucket-subdir DIR]Required Parameters
| ID of the support bundle to modify. |
Options
| Update the prefix for the bundle file name.
|
| Upload support bundle immediately after creation. This option can only be used if the bundle is in CREATING or QUEUED state (you can determine the state using |
| Don't upload support bundle immediately after creation. |
| Delete bundle immediately after it's successfully sent. This option can only be used if the bundle is in CREATING or QUEUED state (you can determine the state using |
| Don't delete bundle immediately after it's successfully sent. |
| Upload non-aggregated support bundle via VMS. This option can only be used if the bundle is in CREATING or QUEUED state (you can determine the state using |
| Don't upload non-aggregated support bundle via VMS. |
| Specify the access key of a valid key pair for accessing the destination S3 bucket. This option can only be used if the bundle is in CREATING or QUEUED state (you can determine the state using |
| Specify the secret key of a valid key pair for accessing the destination S3 bucket. This option can only be used if the bundle is in CREATING or QUEUED state (you can determine the state using |
| Specify the S3 bucket name of the destination S3 bucket. This option can only be used if the bundle is in CREATING or QUEUED state (you can determine the state using |
| Upload support bundle to a subdirectory under support bucket. This option can only be used if the bundle is in CREATING or QUEUED state (you can determine the state using |
Example
This example shows how to modify a support bundle to trigger an immediate upload (after creation) to the configured target bucket destination:
vcli: admin> supportbundle modify --id 123 --send-now