Architecture names reset to 'Architecture [number]' in CalmHub UI when pushing second version

[willosborne]

Bug Report

Steps to Reproduce:

1. Launch a fresh calm hub from calm-hub/deploy > docker compose up. Make sure you delete your DB if it already exists in docker desktop
2. npm ci && npm run build && npx link cli to get latest cli built
3. Load UI and confirm only one archtecture exists under workshop: Conference Signup Architecture
4. push the architecture file linked at the bottom of the issue: npx calm hub push architecture test.arch.json
5. Open CalmHub UI on http://localhost:8080/ and look under workshop namespace > Architectures
6. Name should be correct - Testing Architecture listed.
7. Push it again. npx calm hub push architecture test.arch.json
8. Refresh the page.

Expected Result:

UI should be the same, but one extra version under Test Architecture.

Actual Result:

Test Architecture renamed in UI to 'Architecture 3'.

NB: before pushing the second version, UI was returning right metadata:

Environment:

• Latest main CalmHub
• MacOSX 15.7.3
• Firefox

Additional Context:

NB this is actually returned from the CalmHub API. I think this is not a UI bug.
I can't reproduce this for patterns.

[willosborne]

test.arch.json:

{
  "nodes": [
    {
      "unique-id": "conference-website",
      "name": "Conference Website",
      "description": "Website to sign up for a conference",
      "node-type": "webclient",
      "interfaces": [
        {
          "unique-id": "conference-website-url",
          "url": "http://website.com"
        }
      ]
    },
    {
      "unique-id": "load-balancer",
      "name": "Load Balancer",
      "description": "The attendees service, or a placeholder for another application",
      "node-type": "network",
      "interfaces": [
        {
          "unique-id": "load-balancer-host-port",
          "host": "http://load-balancer/",
          "port": 1234
        }
      ]
    },
    {
      "unique-id": "attendees",
      "name": "Attendees Service",
      "description": "The attendees service, or a placeholder for another application",
      "node-type": "service",
      "interfaces": [
        {
          "unique-id": "attendees-image",
          "image": "[[ IMAGE ]]"
        },
        {
          "unique-id": "attendees-port",
          "port": -1
        }
      ]
    },
    {
      "unique-id": "attendees-store",
      "name": "Attendees Store",
      "description": "Persistent storage for attendees",
      "node-type": "database",
      "interfaces": [
        {
          "unique-id": "database-image",
          "image": "[[ IMAGE ]]"
        },
        {
          "unique-id": "database-port",
          "port": -1
        }
      ]
    },
    {
      "unique-id": "k8s-cluster",
      "name": "Kubernetes Cluster",
      "description": "Kubernetes Cluster with network policy rules enabled",
      "node-type": "system"
    }
  ],
  "relationships": [
    {
      "unique-id": "conference-website-load-balancer",
      "description": "Request attendee details",
      "protocol": "HTTPS",
      "relationship-type": {
        "connects": {
          "source": {
            "node": "conference-website"
          },
          "destination": {
            "node": "load-balancer"
          }
        }
      }
    },
    {
      "unique-id": "load-balancer-attendees-service",
      "description": "Forward",
      "protocol": "mTLS",
      "relationship-type": {
        "connects": {
          "source": {
            "node": "load-balancer"
          },
          "destination": {
            "node": "attendees"
          }
        }
      }
    },
    {
      "unique-id": "attendees-attendees-store",
      "description": "Store or request attendee details",
      "protocol": "JDBC",
      "relationship-type": {
        "connects": {
          "source": {
            "node": "attendees"
          },
          "destination": {
            "node": "attendees-store"
          }
        }
      }
    },
    {
      "unique-id": "deployed-in-k8s-cluster",
      "description": "Components deployed on the k8s cluster",
      "relationship-type": {
        "deployed-in": {
          "container": "k8s-cluster",
          "nodes": [
            "load-balancer",
            "attendees",
            "attendees-store"
          ]
        }
      }
    }
  ],
  "metadata": [
    {
      "kubernetes": {
        "namespace": "conference"
      }
    }
  ],
  "$schema": "http://localhost:8080/calm/namespaces/workshop/patterns/test-pattern/versions/1.0.0",
  "$id": "http://localhost:8080/calm/namespaces/workshop/architectures/test-architecture/versions/1.0.0",
  "title": "Testing architecture",
  "description": "Simple test architecture based on the test pattern."
}

[willosborne]

Having a look at this.

[willosborne]

When architectures are returned from the /api/calm endpoint, the 'name' of resources created via the CLI seems to be null if multiple versions exist.
That means it falls back to the default name of 'Architecture N'.