10 KiB
@backstage/techdocs-common
0.4.0
Minor Changes
08142b256: URL Preparer will now use proper etag based caching introduced in https://github.com/backstage/backstage/pull/4120. Previously, builds used to be cached for 30 minutes.
Patch Changes
77ad0003a: Revert AWS SDK version to v208142b256: TechDocs will throw warning in backend logs when legacy git preparer or dir preparer is used to preparer docs. Migrate to URL Preparer by updatingbackstage.io/techdocs-refannotation to be prefixed withurl:. Detailed docs are here https://backstage.io/docs/features/techdocs/how-to-guides#how-to-use-url-reader-in-techdocs-prepare-step See benefits and reason for doing so https://github.com/backstage/backstage/issues/4409- Updated dependencies [
ffffea8e6] - Updated dependencies [
82b2c11b6] - Updated dependencies [
965e200c6] - Updated dependencies [
ffffea8e6] - Updated dependencies [
5a5163519]- @backstage/backend-common@0.5.3
- @backstage/integration@0.4.0
0.3.7
Patch Changes
c777df180: 1. Added option to use Azure Blob Storage as a choice to store the static generated files for TechDocs.e44925723:techdocs.requestUrlandtechdocs.storageUrlare now optional configs and the discovery API will be used to get the URL where techdocs plugin is hosted.f0320190d: dir preparer will use URL Reader in its implementation.- Updated dependencies [
c4abcdb60] - Updated dependencies [
2430ee7c2] - Updated dependencies [
6e612ce25] - Updated dependencies [
025e122c3] - Updated dependencies [
064c513e1] - Updated dependencies [
7881f2117] - Updated dependencies [
3149bfe63] - Updated dependencies [
2e62aea6f] - Updated dependencies [
11cb5ef94]- @backstage/integration@0.3.2
- @backstage/backend-common@0.5.2
- @backstage/catalog-model@0.7.1
0.3.6
Patch Changes
9dd057662: Upgrade git-url-parse to v11.4.4 which fixes parsing an Azure DevOps branch ref.db2328c88: Add rate limiter for concurrent execution of file uploads in AWS and Google publishers- Updated dependencies [
26a3a6cf0] - Updated dependencies [
664dd08c9] - Updated dependencies [
6800da78d] - Updated dependencies [
9dd057662]- @backstage/backend-common@0.5.1
- @backstage/integration@0.3.1
0.3.5
Patch Changes
-
53c9c51f2: TechDocs backend now streams files through from Google Cloud Storage to the browser, improving memory usage. -
a5e27d5c1: Create type for TechDocsMetadata (#3716)This change introduces a new type (TechDocsMetadata) in packages/techdocs-common. This type is then introduced in the endpoint response in techdocs-backend and in the api interface in techdocs (frontend).
-
Updated dependencies [
def2307f3] -
Updated dependencies [
0b135e7e0] -
Updated dependencies [
294a70cab] -
Updated dependencies [
fa8ba330a] -
Updated dependencies [
0ea032763] -
Updated dependencies [
5345a1f98] -
Updated dependencies [
ed6baab66] -
Updated dependencies [
09a370426] -
Updated dependencies [
a93f42213]- @backstage/catalog-model@0.7.0
- @backstage/backend-common@0.5.0
- @backstage/integration@0.3.0
0.3.4
Patch Changes
a594a7257: @backstage/techdocs-common can now be imported in an environment without @backstage/plugin-techdocs-backend being installed.
0.3.3
Patch Changes
-
68ad5af51: Improve techdocs-common Generator API for it to be used by techdocs-cli. TechDocs generator.run function now takes an input AND an output directory. Most probably you use techdocs-common via plugin-techdocs-backend, and so there is no breaking change for you. But if you use techdocs-common separately, you need to create an output directory and pass into the generator. -
371f67ecd: fix to-string breakage of binary files -
f1e74777a: Fix bug where binary files (png, etc.) could not load when using AWS or GCS publisher. -
dbe4450c3: Google Cloud authentication in TechDocs has been improved.-
techdocs.publisher.googleGcs.credentialsis now optional. If it is missing,GOOGLE_APPLICATION_CREDENTIALSenvironment variable (and some other methods) will be used to authenticate. Read more here https://cloud.google.com/docs/authentication/production -
techdocs.publisher.googleGcs.projectIdis no longer used. You can remove it from yourapp-config.yaml.
-
-
5826d0973: AWS SDK version bump for TechDocs. -
b3b9445df: AWS S3 authentication in TechDocs has been improved.-
techdocs.publisher.awsS3.bucketNameis now the only required config.techdocs.publisher.awsS3.credentialsandtechdocs.publisher.awsS3.regionare optional. -
If
techdocs.publisher.awsS3.credentialsandtechdocs.publisher.awsS3.regionare missing, the AWS environment variablesAWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEYandAWS_REGIONwill be used. There are more better ways of setting up AWS authentication. Read the guide at https://backstage.io/docs/features/techdocs/using-cloud-storage
-
-
Updated dependencies [
466354aaa] -
Updated dependencies [
f3b064e1c] -
Updated dependencies [
abbee6fff] -
Updated dependencies [
147fadcb9]- @backstage/integration@0.2.0
- @backstage/catalog-model@0.6.1
- @backstage/backend-common@0.4.3
0.3.2
Patch Changes
7ec525481: 1. Added option to use AWS S3 as a choice to store the static generated files for TechDocs.f8ba88ded: Fix forintegration.github.apiBaseUrlconfiguration not properly overriding apiBaseUrl used by techdocs00042e73c: Moving the Git actions to isomorphic-git instead of the node binding version of nodegit- Updated dependencies [
5ecd50f8a] - Updated dependencies [
00042e73c] - Updated dependencies [
0829ff126] - Updated dependencies [
036a84373]- @backstage/backend-common@0.4.2
- @backstage/integration@0.1.5
0.3.1
Patch Changes
-
8804e8981: Using @backstage/integration package for GitHub/GitLab/Azure tokens and request options.Most probably you do not have to make any changes in the app because of this change. However, if you are using the
DirectoryPreparerorCommonGitPreparerexported by@backstage/techdocs-commonpackage, you now need to add pass in aconfig(from@backstage/config) instance as argument.<!-- Before --> const directoryPreparer = new DirectoryPreparer(logger); const commonGitPreparer = new CommonGitPreparer(logger); <!-- Now --> const directoryPreparer = new DirectoryPreparer(config, logger); const commonGitPreparer = new CommonGitPreparer(config, logger);
0.3.0
Minor Changes
-
a8573e53b: techdocs-backend: Simplified file, removing individual preparers and generators. techdocs-backend: UrlReader is now available to use in preparers.In your Backstage app,
packages/backend/plugins/techdocs.tsfile has now been simplified, to remove registering individual preparers and generators.Please update the file when upgrading the version of
@backstage/plugin-techdocs-backendpackage.const preparers = await Preparers.fromConfig(config, { logger, reader, }); const generators = await Generators.fromConfig(config, { logger, }); const publisher = await Publisher.fromConfig(config, { logger, discovery, });You should be able to remove unnecessary imports, and just do
import { createRouter, Preparers, Generators, Publisher, } from '@backstage/plugin-techdocs-backend';
0.2.0
Minor Changes
-
dae4f3983: Breaking changes-
Added option to use Google Cloud Storage as a choice to store the static generated files for TechDocs. It can be configured using
techdocs.publisher.typeoption inapp-config.yaml. Step-by-step guide to configure GCS is available here https://backstage.io/docs/features/techdocs/using-cloud-storage Settechdocs.publisher.typeto'local'if you want to continue using local filesystem to store TechDocs files. -
techdocs.builderis now required and can be set to'local'or'external'. (Set it to'local'for now, since CI/CD build workflow for TechDocs will be available soon (in few weeks)). If builder is set to 'local' and you open a TechDocs page,techdocs-backendwill try to generate the docs, publish to storage and show the generated docs afterwords. If builder is set to'external',techdocs-backendwill only fetch the docs and will NOT try to generate and publish. In this case of'external', we assume that docs are being built in the CI/CD pipeline of the repository. TechDocs will not assume a default value fortechdocs.builder. It is better to explicitly define it in theapp-config.yaml. -
When configuring TechDocs in your backend, there is a difference in how a new publisher is created.
--- const publisher = new LocalPublish(logger, discovery); +++ const publisher = Publisher.fromConfig(config, logger, discovery);Based on the config
techdocs.publisher.type, the publisher could be either Local publisher or Google Cloud Storage publisher.-
techdocs.storageUrlis now a required config. Should behttp://localhost:7000/api/techdocs/static/docsin most setups. -
Parts of
@backstage/plugin-techdocs-backendhave been moved to a new package@backstage/techdocs-commonto generate docs. Also to publish docs to-and-fro between TechDocs and a storage (either local or external). However, a Backstage app does NOT need to import thetechdocs-commonpackage - app should only import@backstage/plugin-techdocsand@backstage/plugin-techdocs-backend.
Patch changes
-
See all of TechDocs config options and its documentation https://backstage.io/docs/features/techdocs/configuration
-
Logic about serving static files and metadata retrieval have been abstracted away from the router in
techdocs-backendto the instance of publisher. -
Removed Material UI Spinner from TechDocs header. Spinners cause unnecessary UX distraction. Case 1 (when docs are built and are to be served): Spinners appear for a split second before the name of site shows up. This unnecessarily distracts eyes because spinners increase the size of the Header. A dot (.) would do fine. Definitely more can be done. Case 2 (when docs are being generated): There is already a linear progress bar (which is recommended in Storybook).
-