You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,9 @@ First, you need to have an integration access token - which you can get from htt
8
8
9
9
By default integrations cant access any content so you you *must* share your database (or the parent page / tree it is contained within) with the integration you created earlier to be able to access it.
10
10
11
-
## Notion Database
11
+
## Notion Databases
12
12
13
-
This action expects a Notion database with the following properties:
13
+
This action expects a Notion database with the following properties, this will become the
14
14
15
15
- Name: text
16
16
- Description: text
@@ -30,6 +30,19 @@ It looks like this after it has run:
30
30
31
31
<imgwidth="1451"alt="Screenshot 2021-12-19 at 12 55 39"src="https://user-images.githubusercontent.com/239305/146673989-01187d53-d2fd-42ba-9968-31442b8cc92d.png">
32
32
33
+
## Relation Databases
34
+
35
+
You have an option to provide additional 'lookup' databases to convert some of the above selects into relations:
36
+
37
+
### Segment, Team, System
38
+
39
+
1. Create a database that has *at least* a `Name` column that is unique, all other columns are up to you.
40
+
2. Create an 'Unknown' row - this is what services that cannot be mapped go to (this name matters).
41
+
3. In the config of the action, provide the input variable `segment_database` pointing to this database.
42
+
4. In the main service catalogue table convert the `Segment` column to a relation, pointing at the above database.
43
+
44
+
This can be repeated for `Team` and `System`. The full config is below in the usage.
45
+
33
46
## Service Descriptor Format
34
47
35
48
This action expects each of your repositories to have a descriptor file format in the root of the repo in the form of a Backstage `catalog-info` file. This is because we are testing this approach against using Backstage directly, and wanted to leverage a format that perhaps has a chance of becoming a defacto standard. It does not currently map all fields from Backstage, but if you look at the code you can see what it does map. I may add a config option to allow mapping to be more dynamic in future (a good PR!).
0 commit comments