Hi,
> *Hi,* > > *micro-gw set-project <project_name>* > I think setting the project name we can do within the *micro-gw setup* > command itself rather having another command. > *micro-gw setup <project_name> -a <API_name> -oa <path_to_swagger_file> -e > <endpoint>* > Yes, we can do that in this case. But if you want to switch between different projects, we can't use the setup command again and again. The setup command will work with the command -f. I don't think we can ask the user to use -f for switching between projects. Hence, we would need another command to set the project. Other than @Pubudu Gunatilaka <[email protected]> 's solution, I would like to add another option which is available. We can set up the project folder and then ask the user to go inside that directory if he is willing to do any operation related to the project. As an example, we can consider Git. When the git clone command is executed, it creates a separate folder and the .git file is located inside. Any git command related to the project should be executed within that directory. We can follow the same. > Can we have API_name different from the title in the swagger file? > I think if a different name is provided in the command, precedence will be > given to that API_name. > API Name or any other configs can be specified in the meta-data file. And that file gets the precedence over the swagger. Yes, we can have the API_name from the swagger file. But if we implement so, the user may have to execute another command like "micro-gw list-apis". And that would be a problem if the user needs to automate the process (using shell script). That is the only reason behind providing API_name as command line argument. If it is not a problem, we can proceed without API_name argument. Somehow API_name is not mandatory. I think we have to give precedence to that given API_name. Otherwise, there will be a conflict. Thanks, Viraj On Mon, Feb 25, 2019 at 4:03 PM Pubudu Gunatilaka <[email protected]> wrote: > Hi, > > On Mon, Feb 25, 2019 at 3:41 PM Ishara Cooray <[email protected]> wrote: > >> >> *Hi,* >> >> *micro-gw set-project <project_name>* >> I think setting the project name we can do within the *micro-gw setup* >> command itself rather having another command. >> *micro-gw setup <project_name> -a <API_name> -oa <path_to_swagger_file> >> -e <endpoint>* >> > > Yes, we can do that in this case. But if you want to switch between > different projects, we can't use the setup command again and again. The > setup command will work with the command -f. I don't think we can ask the > user to use -f for switching between projects. > > Hence, we would need another command to set the project. > >> >> Can we have API_name different from the title in the swagger file? >> I think if a different name is provided in the command, precedence will >> be given to that API_name. >> > > API Name or any other configs can be specified in the meta-data file. And > that file get the precedence over the swagger. > > >> >> Current Micro gateway is immutable so that if we want to update an api, >> we will need to re-create the container/instance. >> When we support multiple apis how are we going to handle this? >> In that case i think we may need to have *micro-gw add-api *support for >> bulk of apis. >> > > In the microgateway approach there won't be many APIs and micro-gw add-api > support should be able to handle. > > Thank you! > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Associate Technical Lead > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *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
