Swaroop Raghupathy

fix updateConfigurationChangeResult return code and store task information

1

- [ ] Return HTTP 204 no content for updateConfigurationChangeResult instead of HTTP 200 - [ ] Extend the SERVICE_CONFIGURATION_UPDATE_REQUEST table with TASK_RESULT column and store the `tasks` information from...

make SERVICE_ID column as FK in SERVICE_ORDER table

1

- [ ] Make SERVICE_ID column as a foreign key from DEPLOY_SERIVCE table. - [ ] Ensure purging of a service also purges the SERVICE_ORDER table entries for that service...

SERVICE_CONFIGURATION_UPDATE_REQUEST table shows only one FK index

1

The serviceOrderEntity is linked as a FK in the table but the table definition on the database shows only one FK on the deploy_service table. https://github.com/swaroopar/osc/blob/f1dd0d88c90c05ce0ff9fa8328424c23fb806016/modules/database/src/main/java/org/eclipse/xpanse/modules/database/serviceconfiguration/update/ServiceConfigurationUpdateRequest.java#L57 

add service configuration option to myservices

1

- [ ] add new 'service configuration' option to 'More' drop down. - [ ] On click, a modal must open which has a left Menu. Consider using the antd's...

add config parameters list to service catalog display

1

- [ ] Display service parameter details in table format in all views - register panel, catalog, update, CSP catalog. - [ ] This is something similar to https://github.com/eclipse-xpanse/xpanse/issues/1944 for...

update SERVICE_CONFIGURATION table after completion of config update request

1

SERVICE_CONFIGURATION table holds the current active configuration of the service. Whenever the service config update request is completed, we must updated the configuration information on this table. - [ ]...

store complete service configuration change request information

1

Currently when the `changeServiceConfiguration` is received, we are directly splitting the requests for each configManger and storing it. So there is no table which holds the full request from the...

update terraform-boot and tofu-maker Dockerfiles to support multiple version of tool

1

- [ ] As part of the release build of terraform-boot and tofu-maker, the user can provide the list of versions of the tools that can be installed. - [...

Move deployment information from basic information block

2

- [ ] create new Deployment information block below 'Basic Information' block. - [ ] Use same `Descriptions` antd component to show all deployment information - [ ] Deployerkind -...

use deployer version for all deployment requests

1

After #1939 #1940 #1941 #1942 is implemented, - [ ] compile new interface from terraform-boot and tofu-maker in xpanse. - [ ] pass deployer version in the request to terraform-boot...