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
- Deprecating the `scaffolder.${provider}.token` auth duplication and favoring `integrations.${provider}` instead. If you recieve deprecation warnings your config should change like the following:
9
+
10
+
```yaml
11
+
scaffolder:
12
+
github:
13
+
token:
14
+
$env: GITHUB_TOKEN
15
+
visibility: public
16
+
```
17
+
18
+
To something that looks like this:
19
+
20
+
```yaml
21
+
integration:
22
+
github:
23
+
- host: github.com
24
+
token:
25
+
$env: GITHUB_TOKEN
26
+
scaffolder:
27
+
github:
28
+
visibility: public
29
+
```
30
+
31
+
You can also configure multiple different hosts under the `integration` config like the following:
32
+
33
+
```yaml
34
+
integration:
35
+
github:
36
+
- host: github.com
37
+
token:
38
+
$env: GITHUB_TOKEN
39
+
- host: ghe.mycompany.com
40
+
token:
41
+
$env: GITHUB_ENTERPRISE_TOKEN
42
+
```
43
+
44
+
This of course is the case for all the providers respectively.
45
+
46
+
- Adding support for cross provider scaffolding, you can now create repositories in for example Bitbucket using a template residing in GitHub.
47
+
48
+
- Fix Gitlab scaffolding so that it returns a `catalogInfoUrl` which automatically imports the project into the catalog.
49
+
50
+
- The `Store Path` field on the `scaffolder` frontend has now changed so that you require the full URL to the desired destination repository.
51
+
52
+
`backstage/new-repository`would become `https://github.com/backstage/new-repository` if provider was github for example.
0 commit comments