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

cli: rename config:validate to config:check

Browse Source
This commit is contained in:
Patrik Oldsberg
2020-11-17 18:26:40 +01:00
parent 0b97a89f55
commit 80bf8c7f4f
5 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/conf/defining.md
+3 -3
View File
@@ -85,9 +85,9 @@ declare the visibility of a leaf node of `type: "string"`.
## Validation
Schemas can be validated using the `backstage-cli config:validate` command. If
you want to validate anything else than the default `app-config.yaml`, be sure
to pass in all of the configuration files as `--config <path>` options as well.
Schemas can be validated using the `backstage-cli config:check` command. If you
want to validate anything else than the default `app-config.yaml`, be sure to
pass in all of the configuration files as `--config <path>` options as well.
To validate and examine the frontend configuration, use the
`backstage-cli config:print --frontend` command. Just like for validation you
docs/conf/index.md
+1 -1
View File
@@ -43,7 +43,7 @@ custom `visibility` keyword, as configuration is by default only available in
the backend.
You can validate your configuration against the schema using
`backstage-cli config:validate`, and define a schema for your own plugin either
`backstage-cli config:check`, and define a schema for your own plugin either
using JSON Schema or TypeScript. For more information, see
[Defining Configuration](./defining.md).