You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1/ Recognise the ietf-yang-schema-mount - mount point extension in yang module.
2/ Allow specifying a module as mounted in a mount-point defined by other module in same generation/execution.
The text was updated successfully, but these errors were encountered:
In the attached zip, I have provided a minimal yang model "list-manager" that provides a mountpoint where entry-type-1 and entry-type-2 can be mounted in runtime by a NETCONF / RESTCONF Server.
Since yang2swagger has no support for that now, I have commented 2 lines in list-manager.yang (Line 6 and 46) that imports and declares the mount-point.
To demonstrate how the data structure should be, I have defined the contents of entry-type-1 and entry-type-2 modules inside a grouping and used "uses" in list-manager. See the generated swagger.yaml.
Once this feature is implemented
list-manager should NOT import,use anything from entry-type-1, entry-type-2. It's the server that does the mounting
Swagger-generator when generating the output for module "list-manager", should accept additional yang module names that are getting mounted in the mountpoint "name" (yangmnt:mount-point argument)
The yang modules that are listed as "mounted" should be mounted only and NOT be generated at the root /data level, unless those are also listed for generation.
1/ Recognise the ietf-yang-schema-mount - mount point extension in yang module.
2/ Allow specifying a module as mounted in a mount-point defined by other module in same generation/execution.
The text was updated successfully, but these errors were encountered: