[FOLIO-2908] Allow 204 No Content wo Location for Tenant interface 2.0 Created: 10/Dec/20  Updated: 21/Dec/20  Resolved: 11/Dec/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Adam Dickmeiss Assignee: Adam Dickmeiss
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Text File patch.txt    
Issue links:
Blocks
blocks RMB-775 Updates for sync option for Tenant v2 Closed
Relates
relates to RMB-754 Provide implementation for the async ... Closed
relates to MODINVSTOR-648 Tests on master stuck and then fail Closed
Sprint: CP: sprint 103
Story Points: 1
Development Team: Core: Platform

 Description   

RMB32 implements only the tenant interface 2.0 and can only support that version at a time.

We will add "200 OK" or "204 No content" as a possible response for the v2 tenant.raml in the shared raml and update RMB accordingly. This requires no changes to RMB except an update to the "raml" project.

An RMB based module can, thus, implement postTenant and return the response synchronously. Okapi already allows sync responses and assumes that if no Location is returned, the module has fully performed the tenant init upon completion.



 Comments   
Comment by Jakub Skoczen [ 10/Dec/20 ]

Adam Dickmeiss Wouldn't it make more sense to return "200 OK' with tenantJob.schema and complete=true? How would the module report migration errors?

Comment by Adam Dickmeiss [ 11/Dec/20 ]

Errors are reported with 400 and text/plain. This is old behavior and also the behavior if the async operation could't start.

Generated at Thu Feb 08 23:24:08 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.