A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

Hello, when onboarding new entities, do I have to manually write the <https://github.com/linkedin/datahub/tree/master/gms/api/src/main/idl|restspec.json file> for the new entity in the gms-api module?

Hi Pedro. That should be autogenerated on build if you've defined your resource file (idl and snapshots)

I've defined the pegasus files in the resource folder. Do I need to do more?

Screenshot from 2021-02-11 16-38-06.png

To avoid confusion, <@U01GCJKA8P9> you're saying that a `com.linkedin.stream.streams.restspec.json` should have been created automatically created from the new pegasus files (`Stream` &amp; `StreamKey` )?

I see data templates are automatically generated, the same is not true for the generatedRest classes

You would also need to write the resource (or <http://rest.li|rest.li> end point) .. <https://github.com/linkedin/datahub/blob/master/gms/impl/src/main/java/com/linkedin/metadata/resources/identity/CorpUsers.java|example> ..
idl and snapshots are generated from these resources

<https://github.com/linkedin/datahub/blob/master/gms/impl/src/main/java/com/linkedin/metadata/resources/dataset/Datasets.java#L55>

Jinx^ Yes you'll need to implement the endpoint itself

Restli will then autogenerate the specs from this class^

Thank you both! I think this part is missing from <https://raw.githubusercontent.com/linkedin/datahub/master/docs/imgs/onboard-a-new-entity.png> or the order of steps is different in step 4

Agree -- looks like 4.5 hints at it but it should be much more explicit

Please bear with me as a I go through this process. Your help has been invaluable!

Your feedback continues to be invaluable :slightly_smiling_face: