Nolan Brubaker 09bbe072cd Check errors when closing GCP objects ...

Writing to GCP's object store is any async operation, so errors need to
be checked both on write and close calls, since errors like permission
violations aren't reported until a close.

Signed-off-by: Nolan Brubaker <nolan@heptio.com>

2018-05-22 17:38:49 -04:00

..

apis/ark/v1

regenerate code with updated generator

2018-04-20 12:59:22 -07:00

backup

Merge pull request #484 from nrb/move-groupresources

2018-05-15 14:02:29 -07:00

buildinfo

make language and casing consistent across copyrights

2018-01-02 10:51:49 -08:00

client

Add global kubecontext CLI flag

2018-02-26 10:47:39 -08:00

cloudprovider

Check errors when closing GCP objects

2018-05-22 17:38:49 -04:00

cmd

Merge pull request #496 from nrb/fix-477

2018-05-17 13:23:23 -04:00

controller

Merge pull request #500 from nrb/fix-497

2018-05-17 14:23:41 -04:00

discovery

Expand required resource verbs with get and delete

2018-05-15 10:55:03 -04:00

generated

regenerate code with updated generator

2018-04-20 12:59:22 -07:00

install

Add library code to install required server components

2018-05-18 14:43:06 -06:00

kuberesource

Consolidate commonly used GroupResource objects

2018-05-15 15:55:15 -04:00

plugin

cleanup plugin subprocesses on server exit

2018-05-11 09:48:46 -07:00

restore

Consolidate commonly used GroupResource objects

2018-05-15 15:55:15 -04:00

util

Consolidate commonly used GroupResource objects

2018-05-15 15:55:15 -04:00