refactor(backstage): simplify dev bootstrap and use remote catalog templates

- Always rebuild the Backstage Docker image to ensure consistency during local development
- Remove references to local example files in app-configs
- Use remote GitHub URL for centralized catalog templates
- Add NODE_OPTIONS to ConfigMap to prevent node snapshot issues

Author: wnqueiroz

.bootstrap/backstage/manifests/config-map.yaml

@@ -4,5 +4,6 @@ metadata:
   name: backstage-config
   namespace: backstage-system
 data:
+  NODE_OPTIONS: --no-node-snapshot
   POSTGRES_HOST: postgres.backstage-system.svc.cluster.local
   POSTGRES_PORT: "5432"

.bootstrap/backstage/up.sh

@@ -28,17 +28,13 @@ else
     echo "✅ Namespace $NS already exists."
 fi
 
-# Build Docker image only if it doesn't already exist
-if ! docker image inspect "$IMAGE" >/dev/null 2>&1; then
-    echo "Building Backstage image $IMAGE..."
-    cd "./backstage"
-    yarn build:all
-    yarn build-image --tag "$IMAGE" --no-cache
-    kind load docker-image "$IMAGE" --name "$CLUSTER_NAME"
-    cd ..
-else
-    echo "✅ Docker image $IMAGE already exists. Skipping build."
-fi
+echo "Building Backstage image $IMAGE..."
+cd ./backstage
+docker rmi -f $IMAGE
+yarn build:all
+yarn build-image --tag "$IMAGE" --no-cache
+kind load docker-image "$IMAGE" --name "$CLUSTER_NAME"
+cd ..
 
 # Apply manifests to the cluster (idempotent)
 echo "Applying manifests from $MANIFESTS_DIR..."

backstage/app-config.production.yaml

@@ -42,19 +42,8 @@ catalog:
   # See https://backstage.io/docs/features/software-catalog/#adding-components-to-the-catalog for more details
   # on how to get entities into the catalog.
   locations:
-    # Local example data, replace this with your production config, these are intended for demo use only.
-    # File locations are relative to the backend process, typically in a deployed context, such as in a Docker container, this will be the root
-    - type: file
-      target: ./examples/entities.yaml
-
-    # Local example template
-    - type: file
-      target: ./examples/template/template.yaml
+    # All Templates
+    - type: url
+      target: https://github.com/wnqueiroz/platform-engineering-backstack/blob/main/backstage/catalog/all-templates.yaml
       rules:
         - allow: [Template]
-
-    # Local example organizational data
-    - type: file
-      target: ./examples/org.yaml
-      rules:
-        - allow: [User, Group]

backstage/app-config.yaml

@@ -78,27 +78,27 @@ catalog:
   rules:
     - allow: [Component, System, API, Resource, Location]
   locations:
-    # Local example data, file locations are relative to the backend process, typically `packages/backend`
-    - type: file
-      target: ../../examples/entities.yaml
-
-    # Local example template
-    - type: file
-      target: ../../examples/template/template.yaml
+    # All Templates
+    - type: url
+      target: https://github.com/wnqueiroz/platform-engineering-backstack/blob/main/backstage/catalog/all-templates.yaml
       rules:
         - allow: [Template]
 
-    # Local example template
-    - type: file
-      target: ../../catalog/templates/xqueue-claim/template.yaml
-      rules:
-        - allow: [Template]
+    # Local example data, file locations are relative to the backend process, typically `packages/backend`
+    # - type: file
+    #   target: ../../examples/entities.yaml
 
-    # Local example organizational data
-    - type: file
-      target: ../../examples/org.yaml
-      rules:
-        - allow: [User, Group]
+    # # Local example template
+    # - type: file
+    #   target: ../../examples/template/template.yaml
+    #   rules:
+    #     - allow: [Template]
+
+    # # Local example organizational data
+    # - type: file
+    #   target: ../../examples/org.yaml
+    #   rules:
+    #     - allow: [User, Group]
 
     ## Uncomment these lines to add more example data
     # - type: url