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

Modifiability of data with in a Template (living templates) #7

Open
shiyaashrf opened this issue Nov 13, 2024 · 6 comments
Open

Modifiability of data with in a Template (living templates) #7

shiyaashrf opened this issue Nov 13, 2024 · 6 comments

Comments

@shiyaashrf
Copy link

shiyaashrf commented Nov 13, 2024

Requirements

It must be possible to modify the data (i.e add/modify/delete data nodes) defined in an already existing Template irrespective of whether there are references to it or not.
If there are references to the template, then the modified template data should get expanded for all its existing references.

Non-Requirements

None.

@kwatsen
Copy link

kwatsen commented Nov 13, 2024

If I understand correctly, this is what I've heard called "Living Templates". That is, the template-association is "live" such that any modification to the template immediately impacts all "consumers" of the template. Yes?

@shiyaashrf
Copy link
Author

I dont recall hearing the term "Living Templates". But from your explanation, I think I meant the same requirement.

@kwatsen kwatsen changed the title Modifiability of data with in a Template. Modifiability of data with in a Template (living templates) Nov 13, 2024
@kwatsen
Copy link

kwatsen commented Nov 13, 2024

That was the term we used at Juniper. It's not one used (yet) in the IETF. I guess it relates to the template association being long-lived (not just applied once).

@shiyaashrf
Copy link
Author

Ok. I guess we are inline on this.

@jsterne
Copy link

jsterne commented Nov 14, 2024

Is another way to say this simply that the template is expanded every time a commit occurs?

@kwatsen
Copy link

kwatsen commented Nov 14, 2024

Indeed, it is expanded (in ) every time a commit occurs, because is subject to validation.

That said, in some implementations, may be ephemeral. In such cases, the templates are also expanded every time a client gets .

So there's two cases when templates may be expanded.

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

3 participants