Skip to content

Issues: netmod-wg/template-reqs

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
20 Open 1 Closed
20 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Templates must be able to reference other templates (hierarchal templates)
#2 opened Nov 13, 2024 by kwatsen updated Jan 7, 2025
2
Support basic programmatic elements in templates
#8 opened Nov 13, 2024 by xorrkaz updated Jan 7, 2025
1
Wherever a template-reference can occur, more than one template-reference can occur (and they are applied)
#1 opened Nov 13, 2024 by kwatsen updated Feb 17, 2025
1
Templates must work with any YANG module (including augments and deviations)
#3 opened Nov 13, 2024 by kwatsen updated Feb 17, 2025
3
Template syntax must be validated when defined (not only when used)
#4 opened Nov 13, 2024 by kwatsen updated Feb 17, 2025
5
Wherever a template-reference can occur, it must be possible to delete nodes from the template.
#5 opened Nov 13, 2024 by kwatsen updated Feb 17, 2025
8
Local-config overrides template-config
#6 opened Nov 13, 2024 by derajara updated Feb 17, 2025
Templates are persistent (living templates) modifications to them are automatically applied to all consumers
#7 opened Nov 13, 2024 by shiyaashrf updated Feb 17, 2025
6
It must be possible to constrain which nodes can be template-consumers
#9 opened Nov 14, 2024 by jsterne updated Feb 17, 2025
1
The <running> datastore contains the unexpanded template
#12 opened Dec 1, 2024 by kwatsen updated Feb 18, 2025
4
When templates are applied at multiple ancestor nodes, the innermost (closest) template takes precedence.
#20 opened Feb 27, 2025 by jsterne updated Feb 27, 2025
Possibility to reorder some user-ordered list/leaf-list entries defined in a template
#11 opened Nov 15, 2024 by QiufangMa updated Feb 27, 2025
3
For living templates, the configuration with both unexpanded and expanded templates is able to be returned
#10 opened Nov 15, 2024 by QiufangMa updated Feb 27, 2025
3
For NMDA, the <intended> datastore returns the expanded template
#13 opened Dec 1, 2024 by kwatsen updated Feb 27, 2025
11
Off-box template-expansion of <running> containing templates must be possible (potentially enabling off-box validation)
#14 opened Dec 1, 2024 by kwatsen updated Feb 27, 2025
2
For NMDA, the <intended> datastore returns the unexpanded templates
#15 opened Dec 4, 2024 by kwatsen updated Feb 27, 2025
6
For NMDA, The <operational> datastore returns unexpanded template config (depends on #15)
#17 opened Feb 17, 2025 by jsterne updated Feb 27, 2025
2
Support limited-regex in template-config for template-consumer application
#18 opened Feb 19, 2025 by kwatsen updated Feb 27, 2025
1
When multiple templates are applied to a node, a precedence order must be defined (either ascending or descending)
#19 opened Feb 27, 2025 by jsterne updated Feb 27, 2025
The solution enables non-nmda servers to return the expanded data
#21 opened Feb 27, 2025 by derajara updated Feb 27, 2025
1
ProTip! no:milestone will show everything without a milestone.