DImuthuUpe opened a new pull request, #712: URL: https://github.com/apache/airavata/pull/712
## Summary Squashed **port** of the `research-api-v2` work (originally 17 commits by @krishkatariya / katamyra fork) onto the re-architected `apache/master`. Authorship is preserved via `Co-authored-by` on the single squashed commit. The original work lived in `modules/research-framework/research-service`, which no longer exists on `master` after the module-flattening / gRPC re-architecture. This PR relocates the Spring Boot **REST v2 API** for compute/storage resources into `airavata-api/research-service`. ## What's included - v2 REST controllers (`ComputeResourceController`, `StorageResourceController`) - DTOs, handlers, JPA repositories, `DTOConverter` - Security/auth config (API key + Authz token filters, custom entry point) - Dataset / dev-data initializers, `DevAuthController` - DB migration: increase description column lengths - `.gitignore`: ignore `/airavata-api/distribution/` ## ⚠️ Deferred — needs maintainer reconciliation This is a **draft** because `master` was rearchitected (REST/JPA → gRPC, monolithic registry entities → per-service model modules). The following were intentionally **not** auto-resolved: 1. **`pom.xml` / `README.md`** — apache's existing gRPC `research-service` versions were kept; katamyra's Maven deps for the REST module still need to be merged in. 2. **Appcatalog entity edits** — the 34 edits under `registry/core/entities/appcatalog/*` were **omitted**; those entities were split into `airavata-api/compute-service/.../compute/model` and `storage-service/.../storage/model` with new packages and must be re-applied there. 3. **REST-vs-gRPC overlap** — both this work and master occupy `org.apache.airavata.research.service`; the REST layer and the new gRPC services need architectural reconciliation. A backup of the original branch state exists locally. Happy to adjust the porting approach based on maintainer preference. -- 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]
