-
Notifications
You must be signed in to change notification settings - Fork 85
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 nsxt_edge_transport_node data source #1030
Conversation
2c45492
to
861daac
Compare
/test-all |
861daac
to
49a9141
Compare
/test-all |
"id": getDataSourceIDSchema(), | ||
"display_name": getDataSourceExtendedDisplayNameSchema(), | ||
"description": getDescriptionSchema(), | ||
"node_type": { |
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.
Would it make sense to filter by node type as well?
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.
Would that produce a unique result, other than in testing environments?
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.
Seems to me like such filtering could be helpful, but we can wait for the ask
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.
Maybe it's better to wait and see if we want to convert this into nsxt_edge_transport_node as discussed? Or maybe we change only the resource?
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.
I don't really have a preference, either is fine I think
Signed-off-by: Kobi Samoray <[email protected]>
49a9141
to
5023870
Compare
/test-all |
No description provided.