Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wherever a template-reference can occur, more than one template-reference can occur #1

Open
kwatsen opened this issue Nov 13, 2024 · 0 comments

Comments

@kwatsen
Copy link

kwatsen commented Nov 13, 2024

Requirements

This requirement enables configuration through composition. That is, that the total configuration for some node (and its descendants) may come from more than one template.

For example, assuming YANG for data model for 3-D graphics may require all objects to have a color, material, and a texture defined, but the data model did not define an ability for the color/material/texture to be referenced (i.e., no leafref). It would become tedious to explicitly set the same color/texture/material on many objects, and hence may be desirable to have a template to define a color, a template to define a texture, and a template to define a material, and to have the many objects refer to one of each kind of template to get their final configuration.

Non-Requirements

Implicit in this requirement is a need to define a rule for how overlaps/collisions are handled. For instance, the templates could be ordered or prioritized, with a "last-one wins" approach. Alternately, if the overlap/collision regards a list, it could be that the lists are merged. In any case, this requirement does NOT pick what approach may be used, leaving that decision to be made elsewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant