From c791aa62520a5fb0716172b7a100b47490577e80 Mon Sep 17 00:00:00 2001 From: Wojciech Tyczynski Date: Thu, 6 Jul 2017 14:44:57 +0200 Subject: [PATCH] Rename resource names --- contributors/design-proposals/bulk_watch.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/contributors/design-proposals/bulk_watch.md b/contributors/design-proposals/bulk_watch.md index 64db9053706..ae3d543f65f 100644 --- a/contributors/design-proposals/bulk_watch.md +++ b/contributors/design-proposals/bulk_watch.md @@ -102,10 +102,10 @@ go through alpha and beta stages before (it will start as v1alpha1). Later, we would like to introduce new resources to support bulk create, update and delete operations, but that's not part of this design. - We will start with introducing `getoperation` resource and supporting the + We will start with introducing `bulkgetoperations` resource and supporting the following operation: ``` -POST /apis/bulk.k8s.io/v1/getoperation +POST /apis/bulk.k8s.io/v1/bulkgetoperations ``` We can't simply make this an http GET request, due to limitations of GET for the size (length) of the url (in which we would have to pass filter options). @@ -117,7 +117,7 @@ also need to support). As a result, we need another API for watch that will also support incremental subscriptions - it will look as following: ``` -websocket /apis/bulk.k8s.io/v1/getoperation?watch=1 +websocket /apis/bulk.k8s.io/v1/bulkgetoperations?watch=1 ``` *Note: For consistency, we also considered introducing websocket API for @@ -137,7 +137,7 @@ other Kubernetes APIs as possible. So we define the selector for bulk operations as following: ``` -type GetOperations struct { +type BulkGetOperation struct { Operations []GetOperation }