From fa2d3a21658d3039062890b8ad1ca2f701056147 Mon Sep 17 00:00:00 2001 From: Ali Ok Date: Fri, 20 Sep 2024 15:34:23 +0300 Subject: [PATCH] Update token Signed-off-by: Ali Ok --- blog/docs/articles/knative-backstage-security.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/blog/docs/articles/knative-backstage-security.md b/blog/docs/articles/knative-backstage-security.md index 3542249864..15e44bbbc9 100644 --- a/blog/docs/articles/knative-backstage-security.md +++ b/blog/docs/articles/knative-backstage-security.md @@ -29,7 +29,7 @@ catalog: providers: knativeEventMesh: dev: - token: "eyJhb.........NHA" + token: '${KNATIVE_EVENT_MESH_TOKEN}' baseUrl: "http://eventmesh-backend.knative-eventing.svc:8080" schedule: # optional; same options as in TaskScheduleDefinition # supports cron, ISO duration, "human duration" as used in code @@ -38,6 +38,8 @@ catalog: timeout: { minutes: 1 } ``` +The `token` is taken from the `KNATIVE_EVENT_MESH_TOKEN` environment variable. Backstage supports environment variables in the configuration files, so you can set the token as an environment variable before starting the Backstage instance. Actually, Backstage has other mechanisms, including configuration files, file includes and others. You can check the [Backstage documentation](https://backstage.io/docs/conf/writing/){:target="_blank"} for more information. + How to create the `ServiceAccount`, `ClusterRole`, `ClusterRoleBinding`, `Secret` and the token for that `Secret` is documented in the [plugin's readme file](https://github.com/knative-extensions/backstage-plugins/blob/main/backstage/plugins/knative-event-mesh-backend/README.md). ## Demo and quick start