@backstage/plugin-catalog-backend 0.17.3 → 0.19.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/CHANGELOG.md +129 -0
- package/dist/index.cjs.js +593 -452
- package/dist/index.cjs.js.map +1 -1
- package/dist/index.d.ts +51 -12
- package/package.json +11 -11
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,134 @@
|
|
|
1
1
|
# @backstage/plugin-catalog-backend
|
|
2
2
|
|
|
3
|
+
## 0.19.1
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- dcd1a0c3f4: Minor improvement to the API reports, by not unpacking arguments directly
|
|
8
|
+
- 6bccc7d794: The `pagedRequest` method in the GitLab ingestion client is now public for re-use and may be used to make other calls to the GitLab API. Developers can now pass in a type into the GitLab `paginated` and `pagedRequest` functions as generics instead of forcing `any` (defaults to `any` to maintain compatibility). The `GitLabClient` now provides a `isSelfManaged` convenience method.
|
|
9
|
+
- 0e4daaa753: Reject catalog entities that have duplicate fields that vary only in casing.
|
|
10
|
+
- 98a9c35f0c: Honor database migration configuration
|
|
11
|
+
- Updated dependencies
|
|
12
|
+
- @backstage/backend-common@0.9.13
|
|
13
|
+
|
|
14
|
+
## 0.19.0
|
|
15
|
+
|
|
16
|
+
### Minor Changes
|
|
17
|
+
|
|
18
|
+
- 905dd952ac: **BREAKING** `DefaultCatalogCollator` has a new required option `tokenManager`. See the create-app changelog for how to create a `tokenManager` and add it to the `PluginEnvironment`. It can then be passed to the collator in `createPlugin`:
|
|
19
|
+
|
|
20
|
+
```diff
|
|
21
|
+
// packages/backend/src/plugins/search.ts
|
|
22
|
+
|
|
23
|
+
...
|
|
24
|
+
export default async function createPlugin({
|
|
25
|
+
...
|
|
26
|
+
+ tokenManager,
|
|
27
|
+
}: PluginEnvironment) {
|
|
28
|
+
...
|
|
29
|
+
|
|
30
|
+
indexBuilder.addCollator({
|
|
31
|
+
defaultRefreshIntervalSeconds: 600,
|
|
32
|
+
collator: DefaultCatalogCollator.fromConfig(config, {
|
|
33
|
+
discovery,
|
|
34
|
+
+ tokenManager,
|
|
35
|
+
}),
|
|
36
|
+
});
|
|
37
|
+
|
|
38
|
+
...
|
|
39
|
+
}
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
### Patch Changes
|
|
43
|
+
|
|
44
|
+
- b055a6addc: Align on usage of `cross-fetch` vs `node-fetch` in frontend vs backend packages, and remove some unnecessary imports of either one of them
|
|
45
|
+
- Updated dependencies
|
|
46
|
+
- @backstage/integration@0.6.10
|
|
47
|
+
- @backstage/backend-common@0.9.12
|
|
48
|
+
|
|
49
|
+
## 0.18.0
|
|
50
|
+
|
|
51
|
+
### Minor Changes
|
|
52
|
+
|
|
53
|
+
- 7f82ce9f51: **BREAKING** EntitiesSearchFilter fields have changed.
|
|
54
|
+
|
|
55
|
+
EntitiesSearchFilter now has only two fields: `key` and `value`. The `matchValueIn` and `matchValueExists` fields are no longer are supported. Previous filters written using the `matchValueIn` and `matchValueExists` fields can be rewritten as follows:
|
|
56
|
+
|
|
57
|
+
Filtering by existence of key only:
|
|
58
|
+
|
|
59
|
+
```diff
|
|
60
|
+
filter: {
|
|
61
|
+
{
|
|
62
|
+
key: 'abc',
|
|
63
|
+
- matchValueExists: true,
|
|
64
|
+
},
|
|
65
|
+
}
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
Filtering by key and values:
|
|
69
|
+
|
|
70
|
+
```diff
|
|
71
|
+
filter: {
|
|
72
|
+
{
|
|
73
|
+
key: 'abc',
|
|
74
|
+
- matchValueExists: true,
|
|
75
|
+
- matchValueIn: ['xyz'],
|
|
76
|
+
+ values: ['xyz'],
|
|
77
|
+
},
|
|
78
|
+
}
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
Negation of filters can now be achieved through a `not` object:
|
|
82
|
+
|
|
83
|
+
```
|
|
84
|
+
filter: {
|
|
85
|
+
not: {
|
|
86
|
+
key: 'abc',
|
|
87
|
+
values: ['xyz'],
|
|
88
|
+
},
|
|
89
|
+
}
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
### Patch Changes
|
|
93
|
+
|
|
94
|
+
- 740f958290: Providing an empty values array in an EntityFilter will now return no matches.
|
|
95
|
+
- bab752e2b3: Change default port of backend from 7000 to 7007.
|
|
96
|
+
|
|
97
|
+
This is due to the AirPlay Receiver process occupying port 7000 and preventing local Backstage instances on MacOS to start.
|
|
98
|
+
|
|
99
|
+
You can change the port back to 7000 or any other value by providing an `app-config.yaml` with the following values:
|
|
100
|
+
|
|
101
|
+
```
|
|
102
|
+
backend:
|
|
103
|
+
listen: 0.0.0.0:7123
|
|
104
|
+
baseUrl: http://localhost:7123
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
More information can be found here: https://backstage.io/docs/conf/writing
|
|
108
|
+
|
|
109
|
+
- eddb82ab7c: Index User entities by displayName to be able to search by full name. Added displayName (if present) to the 'text' field in the indexed document.
|
|
110
|
+
- 563b039f0b: Added Azure DevOps discovery processor
|
|
111
|
+
- 8866b62f3d: Detect a duplicate entities when adding locations through dry run
|
|
112
|
+
- Updated dependencies
|
|
113
|
+
- @backstage/errors@0.1.5
|
|
114
|
+
- @backstage/backend-common@0.9.11
|
|
115
|
+
|
|
116
|
+
## 0.17.4
|
|
117
|
+
|
|
118
|
+
### Patch Changes
|
|
119
|
+
|
|
120
|
+
- 5d2a7303bd: This fixes a bug where locations couldn't be added unless the processing engine is started.
|
|
121
|
+
It's now possible to run the catalog backend without starting the processing engine and still allowing locations registrations.
|
|
122
|
+
|
|
123
|
+
This is done by refactor the `EntityProvider.connect` to happen outside the engine.
|
|
124
|
+
|
|
125
|
+
- 06934f2f52: Adjust entity query construction to ensure sub-queries are always isolated from one another.
|
|
126
|
+
- b90fc74d70: adds getDefaultProcessor method to CatalogBuilder
|
|
127
|
+
- Updated dependencies
|
|
128
|
+
- @backstage/catalog-client@0.5.2
|
|
129
|
+
- @backstage/catalog-model@0.9.7
|
|
130
|
+
- @backstage/backend-common@0.9.10
|
|
131
|
+
|
|
3
132
|
## 0.17.3
|
|
4
133
|
|
|
5
134
|
### Patch Changes
|