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.

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

Jump to bottom

Feature Request: please implement the feature and if-feature statements #41

Closed
dcornejo opened this issue Oct 4, 2018 · 2 comments
Closed

Feature Request: please implement the feature and if-feature statements #41

dcornejo opened this issue Oct 4, 2018 · 2 comments

Comments

@dcornejo
Copy link
Contributor

dcornejo commented Oct 4, 2018

many of the IETF YANG models are using these statements now - there is a work-around of recoding the IETF models, but it would be useful to be able to use them as is. we will probably have several models with different features, and rather than maintain separate YANG models, just use if-feature.

the ability to set a feature might be done in the configuration file like CLICON_NACM_MODE is set or maybe in the clixon startup code when a plugin is initialized it could possibly return the features it sets. If you use the latter, I don't think you need to validate the feature name when set, just note that it's set in a list.
@olofhagsand
Copy link
Member

This is a planned feature in Clixon 3.8.

olofhagsand added a commit that referenced this issue Oct 10, 2018
@olofhagsand
* YANG Features
ea77e7f 
  * Yang 1.1 feature and if-feature according to RFC 7950 7.20.1 and 7.20.2.
  * See #41
  * Features are declared via CLICON_FEATURE in the configuration file.
  * logical combination of features not implemented, eg if-feature "not foo or
* Identity without any identityref:s caused SEGV
@olofhagsand
Copy link
Member

Added in develop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dcornejo @olofhagsand