paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 29 Packages Projects Releases Wiki Activity

Add default catalogPath value if missing.

Browse Source 
Currently the following target would give an empty catalogPath:
https://bitbucket.mycompany.com/projects/*/repos/*/
However it's convenient to have a default catalog value, and it would
expand as such:
https://bitbucket.mycompany.com/projects/project-a/repos/repo-b/catalog-info.yaml

Signed-off-by: Otto Nordander <otto.nordander@gmail.com>
This commit is contained in:
Otto Nordander
2021-07-13 15:43:50 +02:00
parent 7a6a3586ac
commit e77670bddd
3 changed files with 36 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/bitbucket/discovery.md
+5 -1
View File
@@ -38,7 +38,11 @@ The target is composed of four parts:
repositories prefixed with `service-`.
- The path within each repository to find the catalog YAML file. This will
usually be `/catalog-info.yaml` or a similar variation for catalog files
stored in the root directory of each repository.
stored in the root directory of each repository. If omitted, the default value
`catalog-info.yaml` will be used. E.g. given that `my-project`and `service-a`
exists, `https://bitbucket.mycompany.com/projects/my-project/repos/service-*/`
will result in:
`https://bitbucket.mycompany.com/projects/my-project/repos/service-a/catalog-info.yaml`.
## Custom repository processing