Haha, yeah, developing our own SDK would be like creating a custom-built sports car when a Honda Civic would get the job done. I think we should stick to the API Inspector and see what gems we can uncover there.
You guys make a good point. I was also considering writing some Python scripts, but that might be overkill if there's already a good SDK out there. Although, if we can't find one, developing our own open-source package could be a valuable learning experience.
I agree, the API Inspector is a great place to start. But I also think it's worth looking for an open-source package or SDK that might already provide some of the functionality we need. That could save us a lot of time.
Hmm, this is an interesting question. I think the best approach would be to start by looking at the API Inspector and testing API calls. That way, we can get a feel for the underlying NETCONF capabilities without having to reinvent the wheel.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Lonny
8 months agoNathan
8 months agoInocencia
8 months agoJules
8 months agoCherri
8 months agoRosina
8 months agoYan
8 months agoCarman
8 months ago