yasithdev opened a new pull request, #178: URL: https://github.com/apache/airavata-portals/pull/178
## Summary Migrate the two deep write families to the gRPC facades: - `ExperimentViewSet` create/update/launch/cancel → `research.create_/update_experiment`, `get_experiment`, `terminate_experiment` - `GroupResourceProfileViewSet` create/update/destroy → `compute.create_/update_/remove_group_resource_profile` + the three `remove_group_*` calls (facade arg order verified; the large OrderedDict→Thrift pre-processing in `perform_update` is unchanged) New `grpc_requests` reverse adapters: `experiment` (+ user-config & computational-resource-scheduling; reuses the input/output reverse adapters), `group_resource_profile` (+ the compute-pref slurm/aws proto **oneof**, reservations, SSH configs, both policy types). GRP protocol enums reuse the inverse name maps from the previous batch; `experiment_type` uses the prefix-tolerant `_proto_enum`. ## Test plan - `manage.py check` clean. - Offline `thrift→proto→thrift` round-trips confirm the `ExperimentType` enum, the userConfiguration/scheduling nesting, and the GRP slurm-union + divergent `JSP_CLOUD` enum all survive. - Live create is backend-blocked for these in the dev env (experiment needs a valid app-interface entity; GRP create needs full user context) — same limitation noted for their reads. Note: `experiment_util.launch/clone` live in the external `airavata_django_portal_sdk` package and are still Thrift (incl. `launchExperiment`) — a separate migration. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
