Object Details UUID

[itdependsnetworks]

User Story

As Austin the Network Automation engineer I am often working within Postman building out my automation
I want to be able to easily visualize the UUID's of objects in the UI
so that when I am building queries in Postman I can quickly copy the UUID to test API calls.
I will know this is done when every detailed object page has the UUID visible.

As P.D. the Plugin Developer I am often working within Postman building out my plugin
I want to be able to easily visualize the UUID's of objects in the UI
so that when I am building queries in Postman I can quickly copy the UUID to test API calls.
I will know this is done when every detailed object page has the UUID visible.

As Nelly the Network Engineer I am often working in GraphQL building out my test queries
I want to be able to easily visualize the UUID's of objects in the UI
so that when I am building my GraphQL queries to test GraphQL against various devices and objects using the query variables
I will know this is done when every detailed object page has the UUID visible.

Database Changes (Optional)

No

External Dependencies (Optional)

No

[glennmatthews]

Thanks for the feature request! In my opinion this would best be implemented as a part of #479.

[jedelman8]

@glennmatthews did this by chance make it into #479 ?

[glennmatthews]

To the best of my knowledge, it did not - it should be an easy addition to make though now that #479 is in place.

[dgarros]

I don't mind doing this one if we can agree on how we want it to look like
After looking at the code, I think it would be easy to add it to the created_updated.html template from core/teemplates/inc

We could add the UUID one the same line as created / updated info

or we could add it below

thoughts ?

[glennmatthews]

It would belong in the base object_detail.html template rather than the inc/created_updated.html template, IMO. Do you think it's visible enough in that location/font? Just to throw another option out there, though perhaps this is too visible... :-)

[jedelman8]

Do you think it's visible enough in that location/font?

How visible do we need this?

I do think those 3 ideas are too much in the user's face.

Here are a few more ideas:

What about the idea of creating a new table (always in the bottom left half of the template beneath tags) called "Details" or "Object Details" and for now, it has one row for UUID? This table could also include date created, last updated, etc. timestamps too.

Another idea is embedding this as the first line within the Change Log tab. Definitely wouldn't be front and center, but once users start to know it's there, they'd know right where it is

One final idea is putting it at the very bottom left not in a table, see below:

[jathanism]

Do you think it's visible enough in that location/font?

How visible do we need this?

I do think those 3 ideas are too much in the user's face.

Here are a few more ideas:

What about the idea of creating a new table (always in the bottom left half of the template beneath tags) called "Details" or "Object Details" and for now, it has one row for UUID? This table could also include date created, last updated, etc. timestamps too.

IMO I think this is the best idea. It's a primary field (the primary key in fact), so it should be up top and prominent. And let's make sure it has a copy button like we have on Device.hostname in the Device detail view.

[glennmatthews]

Implemented in next (upcoming 1.2 release) by #933.