Hello everyone, thanks for the help so far in #all-things-deployment. We successfully deployed datahub so far! 🙂 I'd like to ask a question, about ingestion/lineage. We hooked up lineage to airflow and it has been working flawlessly so far. What we have is that some tasks will fetch data from an API Rest and save this data in a database, having inlets as the api and outlets as the database. I can declare the outlet with a Dataset() obj, but how would I go about the API (inlet)? Should I declare it as a dataset or is there a more specific keyword that will mark it as an api in the UI?

Hey hey! Currently, we don't model "services" in DataHub. But it is something that's come up before. I'm guessing this is something you'd be interested in (feature request? @little-megabyte-1074). Until we have that we'd recommend just using Dataset as that placeholder using which you can establish the lineage link!

Thanks for the info!

Hihi @abundant-policeman-24127! I’ve raised a feature request for ya - feel free to add additional context/upvote/subscribe to it for updates teamwork https://feature-requests.datahubproject.io/b/Developer-Experience/p/support-apis-services-as-an-entity

+1