You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

CPS-679 - Getting issue details... STATUS

Description of the bug

Currently, NCMP does NOT support / slashes in the resource identifier as the OpenAPI definition would regard that as separate REST paths ie. a different rest endpoint

Slashes are currently not supported by open API for path params - https://github.com/OAI/OpenAPI-Specification/issues/892#issuecomment-281170254


Currently supported

/v1/ch/node1/data/ds/ncmp-datastore:passthrough-operational/turing-machine:turing-machine?fields=transition-function?depth=3
Wanted (currently not) supported


/v1/ch/node1/data/ds/ncmp-datastore:passthrough-operational/turing-machine:turing-machine/transition-function?depth=5



Solutions

DescriptionExample
1Change resource Identifier from a path param to a query param in the openapi.yml
Sample of url
ncmp/passthorough:Operational?resourceIdentifer=turingmachine:turingmachine/xyz/abc&query={depth=6,fields=abc/x/y/c}

Sample of definiton in openapi.yaml
resourceIdentifierInPath:
  name: resourceIdentifier
  in: query
  description: Resource identifier to get/set the resource data
  required: true
  schema:
    type: string
2Keep it as path param also but we need to assume that all values after this slash belong to this resource only
/passthorough:Operational/{resource-identifier: .+}.

As it is single param and if you enter the value by url encoding then you have to change spring HttpFirewall 
 final StrictHttpFirewall firewall = new StrictHttpFirewall();
        firewall.setAllowUrlEncodedSlash(true);
3Create a method in the controller without using open apiUse spring mvc to create the endpoint


                
        
    
        


                        
    





    

	

		
    
    
            
  • 
            No labels
        
    •