-
Notifications
You must be signed in to change notification settings - Fork 105
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
Implement Generic Command Modeling #110
Comments
+1 for that feature 👍 |
Hey @brevius - we were discussing this on Telegram the other day, and I agree that we need to genericize the commands so that we end up with built-in commands that are fully validated (and parsed for consumption in a table, where possible), with the ability to add arbitrary commands as well. I've been thinking about various ways to handle this and I think I have some good ideas. I have a lot going on at work in the next couple of weeks, but I'll try to get it done as quickly as possible. |
These are cisco nxos commands but these are my top 3..
|
Something usefull for JunOS: |
What about this issue? Will it be done? |
@streamthing The vast majority of this is done in the v2.0.0 branch. Unfortunately, I've had a number of personal and professional obstacles over the past several months that's prevented me from working on much of anything development-related, hyperglass included. I'm hoping to get back to it very soon, though. The v2.0.0 branch should be usable-ish, you'd just have to really study the codebase to get it working with custom generic commands, as one of the primary things left to do prior to release is write documentation. |
@thatmattlove No problem, I'll wait for v2.0.0. |
See #95
2021 05 27 Edit
I'm modifying this issue to encompass a discussed and highly-requested ability to implement arbitrary commands that are in no way linked to address-family or VRFs, and only optionally use built-in validation.
The text was updated successfully, but these errors were encountered: