Frontend Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, using docker compose
• Docker, single container deploying all components
• npm run start
• Other (please specify below)

Backend (Jet Stream) Deployment type

• Cloud Foundry Application (cf push)
• Kubernetes, using a helm chart
• Docker, using docker compose
• Docker, single container deploying all components
• Other (please specify below)

Expected behaviour

Service plan costs display is consistent over time

Actual behaviour

Service plan costs display is initially truncated, and then properly displayed once a service instance creation screen has shown

Steps to reproduce the behavior

• Deploy a service broker which returns the following V2/catalog payload

{
  "services": [	
    {
      "id": "noop-ondemand-service",
      "name": "noop-ondemand",
      "description": "On demand noop dedicated cluster",
      "bindable": true,
      "plans": [
        {
          "id": "noop-ondemand-plan",
          "name": "default",
          "description": "Default plan (beta).",
          "metadata": {
            "key1": "value1",
            "costs": [
              {
                "amount": {
                  "eur": 48
                },
                "unit": "Monthly"
              }
            ],
            "key2": "value2",
            "displayName": "noop plan display name",
            "bullets": [
              "2GB storage",
              "50 concurrent connections"
            ]
          },
          "free": false
        }
      ],
      "tags": [
        "noop",
        "document"
      ],
      "metadata": {},
      "requires": []
    }
  ]
}

• Go to marketplace
• Display service plans for a given service : the cost is truncated
  
• Start service instance creation workflow: service plan displays correctly
  
• Cancel service instance creation
• Display service plans for the service: cost is not truncated
  

Log output covering before error and any error statements

Insert log hereCopy

Detailed Description

Following #2959
the costs are properly displayed.

Context

Why is this change important to you? How would you use it?

our users see broken costs display in their marketplace. This triggers support requests.

Reproduced with current stable stratos with commit hash a728011

Possible Implementation

Suspecting the create service instance workflow is modifying/normalizing the service catalog data, and that this logic is missing when only displaying service plans

/CC @ldangeard-orange