Ruwan/ Charitha, I don't see the need. When API is being used to create new type definitions, everything needed to create that device type definition is encapsulated there.
So rather than working on an additional API endpoint to do import/export, we should rather advice users to use the script containing APIs to export device types into a new environment. That way we have zero to implement. Only a doc is needed. On Mon, Jan 15, 2018 at 8:28 AM, Ruwan Yatawara <[email protected]> wrote: > Yes, Charitha, I think this is a must-have feature, we should implement. > However, I propose we should provide an archive of sorts (instead of a yaml > file), given that device types can carry their own, UI implementations as > well as analytics scripts and things of that sort. > > IMO, since we already have the OSGI feature based device type deployer, > that does the same thing to an extent; we should build on top of that and > come up with this artifact based model, possible. This will help us get rid > of the feature based device type deployer, in the future. > > I am +1. > > Thanks and Regards, > > Ruwan Yatawara > > Technical Lead, > WSO2 Inc. > > email : [email protected] > mobile : +94 77 9110413 > http://ruwansrants.blogspot.com/ > https://500px.com/ruwan_ace > https://medium.com/@ruwanyatawara > > > On Sun, Jan 14, 2018 at 9:27 PM, Charitha Goonetilleke <[email protected] > > wrote: > >> Hi all, >> >> *Problem:* >> In IoTS we do have capability to define device type via CDMF Device Type >> API[1]. However once we created a device type definition via API, we don't >> have option to export it to another IoTS. Due to that reason, user has to >> manually create Device Type again via Device Management App or the above >> API[1]. >> >> *Solution:* >> Provide Export/Import option to CDMF by introducing a new API endpoint to >> import and export Device Type definition. Device Type definition can be >> exported as yaml test and same can be imported to another IoTS instance. >> Furthermore, UI tool can be provided for the same by consuming >> aforementioned API endpoint. >> >> WDYT? >> >> [1] https://docs.wso2.com/display/IoTS310/Creating+a+New+ >> Device+Type+via+APIs >> >> Thanks & Regards, >> /charithag >> -- >> *Charitha Goonetilleke* >> Senior Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 77 751 3669 <%2B94777513669> >> Twitter:@CharithaWs <https://twitter.com/CharithaWs>, fb: charithag >> <https://www.facebook.com/charithag>, linkedin: charithag >> <http://www.linkedin.com/in/charithag> >> >> <http://wso2.com/signature> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "WSO2 IoT Team Group" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/a/wso2.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "WSO2 IoT Team Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/a/wso2.com/d/optout. > -- --- Sumedha Rubasinghe Director - IoT Architecture, WSO2 m: +94 773017743
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
