Open for Voting
over 2 years ago

More Native Config Change Templates

The idea is to take a few config change templates from thwack, test them and make them native in NCM.

Parents
  • I see that this is one of the top feature requests for NCM.  I'm curious, is the request that we build more config change templates or build more device templates?  The original request was certainly to add more config change templates, but the comments are all around device templates. I suppose one way to distinguish between the two is that adding more device templates will increase the number of vendors and devices that NCM supports, whereas adding more config change templates will improve the depth of support for the existing devices.  So, if we had to prioritize one of the two higher, which would you pick (and why?)

Comment
  • I see that this is one of the top feature requests for NCM.  I'm curious, is the request that we build more config change templates or build more device templates?  The original request was certainly to add more config change templates, but the comments are all around device templates. I suppose one way to distinguish between the two is that adding more device templates will increase the number of vendors and devices that NCM supports, whereas adding more config change templates will improve the depth of support for the existing devices.  So, if we had to prioritize one of the two higher, which would you pick (and why?)

Children
No Data