Closed karthik-sethuraman closed 6 years ago
Hi Karthik, I think it looks good. However, In the previous version of TAPI the context was read only. Is it a decision made by a team to enable modification on data tree for the whole model?
This is a side-effect of YANG requirement that a parent-node should be configurable for any of its children/descendants to be configurable. In previous Yang2Json tool, we handled Context (yang root-node) in a special manner. Any suggestions/fixes welcome. For now, I will manually fix this.
We can put some specific configuration to the tool not to generate some of the CUD operation for specific subtrees. lets take this offline
This might be related with the NMDA architecture: see #283
TAPI OAS specs generated using Eagle Yang2Swagger CLI for TAPI v 1.2.2