Add new ErrMaintenanceInfoConflict failure response

- used when broker receives a request to update / provision a plan with a maintenance info which does not match the broker's catalog [#161178125] Signed-off-by: Kieron Browne <[email protected]> Co-authored-by: Kieron Browne <[email protected]>
pivotal-cf · Dec 7, 2018 · 103135e · 103135e
1 parent ee812b2
commit 103135e
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 0 deletions.
diff --git a/api.go b/api.go
@@ -62,6 +62,7 @@ const (
  invalidServiceID = "invalid-service-id"
  invalidPlanID = "invalid-plan-id"
  concurrentAccessKey = "get-instance-during-update"
+ maintenanceInfoConflictKey = "maintenance-info-conflict"
 )
 
 var (

diff --git a/service_broker.go b/service_broker.go
@@ -210,6 +210,7 @@ const (
  rawInvalidParamsMsg = "The format of the parameters is not valid JSON"
  appGuidMissingMsg = "app_guid is a required field but was not provided"
  concurrentInstanceAccessMsg = "instance is being updated and cannot be retrieved"
+ maintenanceInfoConflictMsg = "passed maintenance_info does not match the catalog maintenance_info"
 )
 
 var (
@@ -259,4 +260,8 @@ var (
  ErrConcurrentInstanceAccess = NewFailureResponseBuilder(
  errors.New(concurrentInstanceAccessMsg), http.StatusUnprocessableEntity, concurrentAccessKey,
  ).WithErrorKey("ConcurrencyError")
+
+ ErrMaintenanceInfoConflict = NewFailureResponseBuilder(
+ errors.New(maintenanceInfoConflictMsg), http.StatusUnprocessableEntity, maintenanceInfoConflictKey,
+ ).WithErrorKey("MaintenanceInfoConflict").Build()
 )