-
Notifications
You must be signed in to change notification settings - Fork 277
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
Store information about NodeGeneration in registry. #1347
Conversation
I have, by the way, taken over the actual view on which nodes are eligable for topology generation. |
takes also already vr-vsrx into account. |
So far generate.go contained two lists indenpendent from the nodes, that would describe nodes that (1) can be generated and (b) what the interface naming convention would be for the node kind. This will introduce seperate fields in the NodeRegistry for this information, such that the information for this sort of node generation can be defined as part of the node definition
dc33e4a
to
8a32cb8
Compare
} | ||
|
||
type GenerateNodeAttributes struct { | ||
generateable bool |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
likely we don't need the generatable
flag at all. All nodes should be generatable, I think some nodes were not generatable originally because we just did not add them manually to the generate cmd
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1347 +/- ##
==========================================
+ Coverage 51.54% 51.76% +0.21%
==========================================
Files 172 172
Lines 16888 16978 +90
==========================================
+ Hits 8705 8788 +83
- Misses 7259 7267 +8
+ Partials 924 923 -1
|
So far generate.go contained two lists indenpendent from the nodes, that would describe nodes that (1) can be generated and (b) what the interface naming convention would be for the node kind. This will introduce seperate fields in the NodeRegistry for this information, such that the information for this sort of node generation can be defined as part of the node definition