Mastering Developer Portals: Discover & Integrate API Schemas with Port

The ability to discover resource definitions makes a huge difference. It allows me to stop wasting my time rewriting "stuff" from one format to another but focus on creating APIs and let others discover what's behind them.

Port just released a feature that enables just that. It allows us to discover schemas from APIs and convert them into data-models and actions.

In this video use the new "discovery" feature in Port to combine it with the whole life-cycle of resources. We'll see how to combine it with Crossplane, Argo CD, GitHub Actions, and, probably, a few other tools. We'll see how we can enable developers to manage anything, be it applications, databases, clusters, or anything else. We are about to build a whole platform, not only the console.

#DeveloperPortal #InfrastructureAsCode #DevOpsAutomation #Crossplane

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsorships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Issues With Developer Portal Consoles
03:04 Discover Data Models From API Schemas
10:07 Create Service Instances
12:46 What Happened?
14:19 How Did It Happen?
19:00 Update and Delete Service Instances

[DevOpsToolkit]

What do you think about "discovery" in Port? How important do you think that feature is?

[martinpetersson]

awesome and love your improvement suggestions. Especially the observability part. Developers must have insights to their resourses they created.

[arieheinrich]

IF only this was not tightly coupled with K8s. K8s should be treated like any API provider, think Terraform structure.
Port should have its own open schema and API.
Not everything sits on k8s or should sit on it. But i would still want to offer these services to devs and more.

Although Viktor wanted self discovery to the UI, please allow presenting the UI in a json for the structure, and the data, think adaptive cards.

[IvanRizzante]

Thanks for another great video! That's actually the "beginning of the end" for other internal developer portal implementations, even with the current downsides it's still very usable!
So we've seen how to build the portal, how to create Crossplane Compositions, and many other things; but what about the GitOps part? How do we define the structure of the GitOps repo to bootstrap the cluster addons? How do we support overrides for multiple environments for these addons? Is it something you have already covered in another video?

[amikhailov]

Does it allow to define "Day 2 operations" for such custom resources? For example, if we speak about databases, as a DBA I'd like to have an ability to run administrative operations (table vacuuming, reindexnig, etc) against databases provisioned from Crossplane provider. I'd like to be able to configure, which cluster the operation should run against, database name, table name and maybe some other flags. Is it possible in Port? And is it possible to link such operations with Crossplane claims?

[KillerBee]

is this sponsored? why are you showing a paid solution? kind of disappointing..