Rename resource names

kubernetes · Jul 6, 2017 · c791aa6 · c791aa6
1 parent 93c1c97
commit c791aa6
Showing 1 changed file with 4 additions and 4 deletions.
diff --git 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 <body defines filtering>
+POST /apis/bulk.k8s.io/v1/bulkgetoperations <body defines filtering>
 ```
  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
 }