Stacked services approach is definitely the way to go with route policies. There are multiple ways t...

You're right. The entire content of the route-policy is modeled as a single string. To handle that i...

The XML processing context is a bit tricky. Using '| debug template' is your best option to understa...

As template engine is traversing the ipv6-addresses, the XML context is changing to point to the cur...

Glad to know you got it solved, and that you got your faith back :) I was a bit late to realize that...

no-deploy was suggested as a way to confirm the behavior - not as a workaround. As mentioned, I'd ex...

Which NSO version are you using? It used to be the case that NSO was, by design, evaluating must sta...

I don't know the exact reason for why you're seeing this behavior, but one thing you can try is to m...

I think it might be possible to find a way to do it using the more advanced template options (if you...

Great! If you'd move the same logic you're already using from create() to premod() you won't have to...

As your service created the device, if you run 'show run devices device my-device | display xml | di...

Two questions here as I see it. First, would it work? Second, is it maintainable? For maintainabilit...

You need to run create on the list, rather than on the list element and provide the element key(s) a...

Are you trying to load netsim devices into NSO or something like that? If so, before you try to use ...