Hi all,

>From the commands mentioned above,  setup command and build command will be
implemented in the newly proposed way as a start. For setup command, it
needs to be compatible for OpenAPI spec 2.0 as well as 3.0. Therefore we
take basepath as a command line argument when the OpenAPI version is 3.0.
Since the previous email contains a large amount of information, I will
repeat the *same information as in the previous email* which is only
relevant to setup and build commands.

   -  *micro-gw setup <project_name>*
      - Project Structure will be created under the provided project name



   -
*micro-gw setup <project_name> -oa <path_to_swagger> -e <endpointConfig> -b
   <basePath> *
      - In this case, the user has to provide the basePath if the OpenAPI
      spec is 3.0 or OpenAPI spec is 2.0 and basePath is not included.
      EndpointConfig is the global endpoint for the API. No ballerina code
      generation happens during the execution of this command. We create the
      folder structure and copy the swagger file into the relevant
directory. In
      the meantime, we will be updating the routes.yaml with global
      configuration. basePath will be saved in the routes.yaml file.
      - API_ID also will be generated using the hash value of
      “API_name:API_version” concatenated string. And the folder in which the
      swagger is saved will be named after that API_ID.
      - routes file will be updated with the basepath variable and the API
      level endpoint under the generated API_ID.



   - *micro-gw set project <project_name>*
      - Since there can be so many projects, the user can specify the
      project he is currently working on so that he does not have to mention
      project name for each and every command repeatedly.



   - *micro-gw build*
      - This will generate the ballerina code, compile the ballerina code
      and after all, we can launch the project.

Thank you,
Viraj

-- 
*Viraj Salaka Gamage* | Software Engineer | WSO2 Inc.
+94 710 618 178
GET INTEGRATION AGILE
Integration Agility for Digitally Driven Business
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to