From 675b5d27692fb315f0a810537e645f102d78d3b7 Mon Sep 17 00:00:00 2001 From: Himanshu Mishra Date: Fri, 11 Dec 2020 10:48:53 +0100 Subject: [PATCH] docs: Add a table for visibility values in our JSON Schema --- docs/conf/defining.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/conf/defining.md b/docs/conf/defining.md index ead5c4ff67..358498929a 100644 --- a/docs/conf/defining.md +++ b/docs/conf/defining.md @@ -83,6 +83,12 @@ object will be available in the frontend. The full ancestry does not need to have correctly defined visibilities however, so it is enough to only for example declare the visibility of a leaf node of `type: "string"`. +| `visibility` | | +| ------------ | ------------------------------------------------------------------ | +| `frontend` | Visible in frontend and backend | +| `backend` | (Default) Only in backend | +| `secret` | Only in backend and may be excluded from logs for security reasons | + ## Validation Schemas can be validated using the `backstage-cli config:check` command. If you