Fix schema for notification routers

pluralsh · Mar 7, 2024 · f165b49 · f165b49
1 parent b8b9488
commit f165b49
Show file tree

Hide file tree

Showing 2 changed files with 23 additions and 3 deletions.
diff --git a/models_gen.go b/models_gen.go
diff --git a/schema/schema.graphql b/schema/schema.graphql
@@ -316,7 +316,7 @@ type RootQueryType {
 
   notificationSinks(after: String, first: Int, before: String, last: Int): NotificationSinkConnection
 
-  notificationRouters(after: String, first: Int, before: String, last: Int): NotificationSinkConnection
+  notificationRouters(after: String, first: Int, before: String, last: Int): NotificationRouterConnection
 
   deploymentSettings: DeploymentSettings
 }
@@ -626,10 +626,10 @@ type RootMutationType {
 
   upsertNotificationSink(attributes: NotificationSinkAttributes!): NotificationSink
 
-  upsertNotificationRouter(attributes: NotificationRouterAttributes!): NotificationRouter
-
   deleteNotificationSink(id: ID!): NotificationSink
 
+  upsertNotificationRouter(attributes: NotificationRouterAttributes!): NotificationRouter
+
   deleteNotificationRouter(id: ID!): NotificationRouter
 
   "a reusable mutation for updating rbac settings on core services"
@@ -872,6 +872,11 @@ type NotificationSinkConnection {
   edges: [NotificationSinkEdge]
 }
 
+type NotificationRouterConnection {
+  pageInfo: PageInfo!
+  edges: [NotificationRouterEdge]
+}
+
 enum RestoreStatus {
   CREATED
   PENDING
@@ -4967,6 +4972,11 @@ type ObjectStoreEdge {
   cursor: String
 }
 
+type NotificationRouterEdge {
+  node: NotificationRouter
+  cursor: String
+}
+
 type NotificationSinkEdge {
   node: NotificationSink
   cursor: String