@jfvilas/plugin-kwirth-backend 0.13.0 → 0.13.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -11,14 +11,17 @@ This [Backstage]((https://backstage.io)) backend plugin is primarily responsible
|
|
|
11
11
|
- Performing login processes to remote Kwirth instances, and thus obtaining valid API keys for users to stream kubernetes data.
|
|
12
12
|
- Receiving and answering API calls from configured frontend Kwirth plugins on your Backstage instance.
|
|
13
13
|
|
|
14
|
+
|
|
14
15
|
## Version compatibility
|
|
15
16
|
Following table shows version compatibility between Kwirth Backstage plugin and Kwirth Core server.
|
|
16
17
|
|
|
17
18
|
| Plugin Kwirth version | Kwirth version |
|
|
18
19
|
|-|-|
|
|
20
|
+
|0.13.0|0.4.131|
|
|
19
21
|
|0.12.8|0.4.45|
|
|
20
22
|
|0.12.6|0.4.20|
|
|
21
23
|
|
|
24
|
+
|
|
22
25
|
## Install plugin
|
|
23
26
|
Here we show how to get this backend plugin up and running quickly. First we need to add the `@jfvilas/plugin-kwirth-backend` package to your Backstage project:
|
|
24
27
|
|
|
@@ -42,6 +45,7 @@ Next, you need to modify your backend index file for starting Kwirth backend plu
|
|
|
42
45
|
backend.start();
|
|
43
46
|
```
|
|
44
47
|
|
|
48
|
+
|
|
45
49
|
## Configure
|
|
46
50
|
To have your Kwirth backend plugins ready for work you must perform some previous additional tasks, like deploying Kwirth, creating API Keys, defining clusters, etc... In this section we cover all these needs in a structured way.
|
|
47
51
|
|