* feat(techdocs): TechDocsPageWrapper to take in labels prop and use TechDocsHeader component
* feat(techdocs): new TechDocsHeader component as wrapper around Header from core
* feat(techdocs): TechDocsPage metadata
* feat(techdocs): TechDocsMetadata class responsible for reading metadata from generated techdocs metadata json file
* fix(techdocs): delete TechDocsPageWrapper component
* fix(app-config): delete /docs from request url
* feat(techdocs): TechDocsHeader with labels to browse metadata
* fix(techdocs): move metadata to backend plugin
* feat(techdocs-backend): introduce two new metadata routes
* feat(techdocs): new techdocs api to be responsible to request metadata from backend
* feat(techdocs): register new api for plugin
* fix(techdocs): reader to take in onReady prop
* fix(techdocs): TechDocsHome component to use its own header
* fix(techdocs): TechDocsPage responsible to get metadata and pass it down to the TechDocsHeader
* fix(techdocs): component tests for both TechDocsHeader and TechDocsPage
* fix(techdocs): adjust api to use /docs in url since it was taken away in requestURL
* fix(tests): move assertion into act
* fix(techdocs): rename TechDocsHeader to TechDocsPageHeader
* fix(techdocs): rename TechDocsHeader to TechDocsPageHeader
* fix(techdocs-backend): add some logs
* Update plugins/techdocs/src/reader/components/TechDocsPage.test.tsx
* delete unused import
* Read from Config for timezone timers
* Remove recusrive dependency on backstage/core and fix tsc errors
* Modify to use ConfigArray instead of fixed Config
* Fix lint and tsc errors
* Cean up app-config.yaml
* add back newline
* Fix prettier error on app-config.yaml
* Address review comments
* Use a flag to determine wether to use techdocs-container or local install of mkdocs
* Updated techdocs generator to look at app-config string instead of argument to decide how to run the generator
* Removed console log...
* Reverted scaffolder file that was accidentally committed.
* Fixed lint issues
* Added config to create-app template
This adds a GitLab integration for the scaffolder backend.
We're introduceing a preparer and a publisher for GitLab so that we can
read templates from GitLab and publish them to a configured GitLab
instance. The two instances don't need to be the same. For instance,
templates could be public on gitlab.com, but the created repos will live
in a hosted GitLab somewhere else.
The publisher gets its own config object in `app-config.yaml` where the
target instance and token can be specified.
The service catalogue defines both `gitlab` and `gitlab/api` as
processors. They are both handled by the same preparer.
Closes#2372
* Added age check for documentation in github to make sure it's up to date
* Updated failing tests
* Updated docs to explain requestUrl and storageUrl
* Updated failing tests
* Update packages/create-app/templates/default-app/app-config.yaml.hbs
* Update docs/features/techdocs/getting-started.md
Co-authored-by: Emma Indal <emmai@spotify.com>
Emma Indal