Closed bpevandro closed 2 years ago
Hi @bpevandro,
Good morning.
I'm not sure if I understand the problem. This is the error is returned by the service and PowerShell CmdLet simply returns it in the output. Do you see the similar error via AWS CLI?
Thanks, Ashish
Think this behavior should be reviewed; we should provide a nicer experience when Read-GLCJobOutput
can't complete because the Job is still in progress.
The job is not currently available for download, it may not have completed: <jobid>
100% agree with @ppittle, this is not the service's API response, this is how Read-GLCJobOutput
is handling it. No reason to print the stack trace at all.
Adding a bit more context. Unlike most of the other PowerShell cmdlets the Read-GLCOutput
is not generated and actually uses the AWS .NET SDK high level library ArchiveTransferManager
. Since it is handcoded that gives us hooks to handle how the service returns back a non 200 status code when requesting to read a job that isn't complete.
We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.
Description
When reading a Glacier vault inventory that has not yet been completed, the CLI outputs errors:
However no error is thrown if the inventory is already completed.
Reproduction Steps
Start-GLCJob -VaultName <vault-name> -JobType inventory-retrieval
Logs
Environment
OS Info: Windows 2k19 Datacenter
This is a :bug: bug-report