@backstage/plugin-events-node 0.4.23-next.0 → 0.4.24-next.0

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # @backstage/plugin-events-node
 
+## 0.4.24-next.0
+
+### Patch Changes
+
+- Updated dependencies
+  - @backstage/backend-plugin-api@1.9.3-next.0
+
+## 0.4.23
+
+### Patch Changes
+
+- Updated dependencies
+  - @backstage/backend-plugin-api@1.9.2
+
 ## 0.4.23-next.0
 
 ### Patch Changes

package/config.schema.json

@@ -0,0 +1,20 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "properties": {
+    "events": {
+      "type": "object",
+      "properties": {
+        "useEventBus": {
+          "type": "string",
+          "enum": [
+            "never",
+            "always",
+            "auto"
+          ],
+          "description": "Whether to use the event bus API in the events plugin backend to distribute events across multiple instances when publishing and subscribing to events.\n\nThe default is 'auto', which means means that the event bus API will be used if it's available, but will be disabled if the events backend returns a 404.\n\nIf set to 'never', the events service will only ever publish events locally to the same instance, while if set to 'always', the event bus API will never be disabled, even if the events backend returns a 404."
+        }
+      }
+    }
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@backstage/plugin-events-node",
-  "version": "0.4.23-next.0",
+  "version": "0.4.24-next.0",
   "description": "The plugin-events-node module for @backstage/plugin-events-backend",
   "backstage": {
     "role": "node-library",
@@ -48,7 +48,7 @@
   },
   "files": [
     "dist",
-    "config.d.ts"
+    "config.schema.json"
   ],
   "scripts": {
     "build": "backstage-cli package build",
@@ -60,7 +60,7 @@
     "test": "backstage-cli package test"
   },
   "dependencies": {
-    "@backstage/backend-plugin-api": "1.9.2-next.0",
+    "@backstage/backend-plugin-api": "1.9.3-next.0",
     "@backstage/errors": "1.3.1",
     "@backstage/types": "1.2.2",
     "@types/content-type": "^1.1.8",
@@ -71,9 +71,9 @@
     "uri-template": "^2.0.0"
   },
   "devDependencies": {
-    "@backstage/backend-test-utils": "1.11.4-next.0",
-    "@backstage/cli": "0.36.3-next.0",
+    "@backstage/backend-test-utils": "1.11.5-next.0",
+    "@backstage/cli": "0.36.4-next.0",
     "msw": "^2.0.0"
   },
-  "configSchema": "config.d.ts"
+  "configSchema": "config.schema.json"
 }

package/config.d.ts

@@ -1,34 +0,0 @@
-/*
- * Copyright 2024 The Backstage Authors
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *     http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
-export interface Config {
-  events?: {
-    /**
-     * Whether to use the event bus API in the events plugin backend to
-     * distribute events across multiple instances when publishing and
-     * subscribing to events.
-     *
-     * The default is 'auto', which means means that the event bus API will be
-     * used if it's available, but will be disabled if the events backend
-     * returns a 404.
-     *
-     * If set to 'never', the events service will only ever publish events
-     * locally to the same instance, while if set to 'always', the event bus API
-     * will never be disabled, even if the events backend returns a 404.
-     */
-    useEventBus?: 'never' | 'always' | 'auto';
-  };
-}