I’m in a new role and learning to use Foundry and today I noticed the Ontology as Code (Beta) link from a menu in Ontology Manager. I have prior experience with IaC - Terraform and aws. My new organisation does everything through the console and I’m curious about OaC.
I see that OaC is in beta - anyone using it? How is it?
If I were to activate it is there an initial export of the code for the ontology in its current state?
I would be grateful to anyone sharing their experience, especially if you can compare to working with terraform. TIA.
2 Likes
I’m VERY excited for this and for the new MCP tools for creating/modifying objects.
Beyond the obvious “config as code” win, the real value is that having schemas/actions as code makes LLMs way better at generating accurate code.
But the biggest win for me: no more clicking through UIs just to add a few fields, context switching between one IDE for my TS frontend, another for my Python transforms.
Go to ontology manager –> New –> Ontology as Code repository
Syntax for defining objects → check the auto-generated template repo or here:
https://github.com/palantir/osdk-ts/blob/main/packages/maker/README.md
Quick setup (VSCode):
-
option + shift + ~ → open terminal
-
npm install → syntax checking
-
done → commit + push → tag → Marketplace → your store → Install
Similarity’s in the eye of your syntax highlighter ;-]
Terraform / Pulumi / SST made infra hell less hellish. Foundry just removes the hell entirely by managing the complexity for you.
Reminds me of my favorite backend for quick weekend builds — Convex — because everything’s code-defined and co-located.
2 Likes
