[ui] Add/Edit service chart values

[richard-cox]

• To flesh out, but the UI side of Allow setting service chart values with CLI epinio#1633
• It's expected these work in the same way as application chart values

Tasks

Beta Give feedback

1. [ui] Supply service chart values when creating a service #338
   kind/enhancement +1
   
2. [ui] Supply service chart values when editing a service #339
   kind/enhancement +1
   
3. [ui] Service/Application charts values, add support for complex types #302
   blocked-backend kind/enhancement +2
   

[richard-cox]

See epinio/epinio#1633 (comment)

[richard-cox]

@torchiaf this will be complete when epinio/epinio#2522 is integrated right?

[thehejik]

Test Report

• seems it works as expected
• So far only simple data types as strings (+ enum), integer (+ minimum, maximum, +enum) and bool are supported, lists and maps should be addressed by [ui] Service/Application charts values, add support for complex types #302
• Unable to Edit deployed service by clicking Edit Config - the values are inactive / grayed out - Added Update and Replace APIs for Service custom values epinio#2522 didn't help when built as epinio-server

Test

• run kubectl edit services.application.epinio.io -n epinio mysql-dev and enter following (settings at values level):

  settings:
    auth.rootPassword:
      type: string
    global.storageClass:
      enum:
      - default
      - local-path
      - none
      type: string
    primary.persistence.enabled:
      type: bool
    primary.service.ports.mysql:
      maximum: "3307"
      minimum: "3306"
      type: integer

• create a new service in UI by using modified mysql-dev service catalog and put reasonable values:
  
• Verify by CLI that the service is deployed and the values are propagated into the service:

$ epinio service show mysql-values-ui

🚢  Showing Service...

✔️  Details:
|       KEY       |                                     VALUE                                      |
|-----------------|--------------------------------------------------------------------------------|
| Name            | mysql-values-ui                                                                |
| Created         | 2023-08-31 16:30:09 +0200 CEST                                                 |
| Catalog Service | mysql-dev                                                                      |
| Version         | 8.0.31                                                                         |
| Status          | deployed                                                                       |
| Used-By         |                                                                                |
| Internal Routes | xefb34329720317139eae966f094d-mysql-headless.workspace.svc.cluster.local:3306, |
|                 | xefb34329720317139eae966f094d-mysql.workspace.svc.cluster.local:3306           |

✔️  Settings
|             KEY             |   VALUE    |
|-----------------------------|------------|
| auth.rootPassword           | linux      |
| global.storageClass         | local-path |
| primary.persistence.enabled | true       |
| primary.service.ports.mysql |       3306 |

✔️  Credentials:
|         KEY         |   VALUE    |
|---------------------|------------|
| mysql-password      | wgPo5Mja1G |
| mysql-root-password | linux      |

[richard-cox]

Edit needs to big integrated / validated now epinio/epinio#2522 has been completed

[richard-cox]

Thinking about it, lets make this issue an epic and create issues for Add (which we can say is complete for 1.10) and Edit (which will probably be for 1.11)

[torchiaf]

@torchiaf this will be complete when epinio/epinio#2522 is integrated right?

Now that 2522 is complete we can go forward with the UI.

[richard-cox]

I've split this out into two issues to denote the milestones each change will go in to

• [ui] Supply service chart values when creating a service #338 (1.10)
• [ui] Supply service chart values when editing a service #339 (1.11)

This epic will be complete when the above is finished and..

• [ui] Service/Application charts values, add support for complex types #302

I've added these as a tasklist in the issue description

[richard-cox]

As part of this issue we should ensure custom chart values are validated as per #299 (comment)

[richard-cox]

Given create and edit are in the code base and tested independently i'm going to close this issue as done.

We still have #302, that is now targeted at 1.12