-
Notifications
You must be signed in to change notification settings - Fork 63
added relation field #11
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
Conversation
|
👍 |
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.
Is this going to have any values such as 'encloses' and 'enclosedBy'?
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.
Right now we make no restrictions on what you add. It all depends on which logic is using it, so feel free to put a stake in the ground as far as conventions for enclosures.
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.
It's unstructured json data that depends on the implementation, basically.
|
@VulpesArtificem As I know, @iceiilin is doing same or similar works on this. could you have a sync to avoid duplicated works? |
|
Is there a spec for this? |
|
@jfrey There is a story tracking this https://hwjiraprd01.corp.emc.com/browse/MAG-176, without detailed spec. I have completed it and intended to open a PR after adding PDU obm settings into enclosure node. For that story, I created a generate-enclosure task to create enclosure info, and it is added to sku discovery workflow. I can open a PR first about enclosure node creation. |
update on-http submodule
https://hwjiraprd01.corp.emc.com/browse/MON-533
@benbp