yasithdev opened a new pull request, #648: URL: https://github.com/apache/airavata/pull/648
Renames the three non-`iam_admin` service protos in iam-service so all of iam-service's gRPC APIs share the `org.apache.airavata.api.iam.*` namespace: `api.userprofile` → `api.iam.userprofile`, `api.sharing` → `api.iam.sharing`, `api.groupmanager` → `api.iam.groupmanager` (`iam_admin_service` already lives at `api.iam`). A single flat `api.iam` is infeasible because `sharing_service` and `group_manager_service` share 17 message names, so the distinct services are nested as siblings under `api.iam`. **This is wire-breaking:** the gRPC service paths change (e.g. `/org.apache.airavata.api.sharing.SharingService/…` → `/org.apache.airavata.api.iam.sharing.SharingService/…`). The in-repo Java consumers are updated (the iam `Sharing`/`GroupManager` gRPC handlers and the launcher's `UserProfileGrpcService`). `compute-service`'s `user_resource_profile_service.proto` keeps `api.userprofile` and is unchanged — it coincidentally shared that Java package with iam's `user_profile_service`, so this rename actually **un-splits** the package across the two modules. The Python SDK gRPC stubs for the three services are regenerated with the matching toolchain (protoc 6.31.1 / grpcio 1.80.0) so the diff is purely the rename; the `.pyi` stubs are unchanged, and importing the regenerated modules confirms the new descriptor packages load cleanly. The full reactor builds green and the iam/compute tests pass. Regenerating the separate-repo portal client is a follow-up. -- 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]
