SuperRepo is in the beta phase of development and may not be available on your enrollment. Functionality may change during active development.
The following questions and answers cover common topics about working with SuperRepos.
Can I migrate existing resources to a SuperRepo?
Existing Ontology entities can be imported into a SuperRepo rather than redefined in code; review Importing for details. Support for additional component types is expanding over time; review Coming in the future for the capabilities currently in development.
Can I edit an object type in Ontology Manager if I created it in a SuperRepo?
No. By default, SuperRepo installations are locked. If you must edit an installed object type directly, you can unlock the project, but edits to an unlocked type are overwritten the next time your SuperRepo is deployed.
Can I define PySpark transforms in a SuperRepo?
No. SuperRepo does not currently support PySpark transforms. Data pipeline support is in development; review Coming in the future for the capabilities currently planned.
Can I publish my SuperRepo from GitHub Actions or CircleCI?
Yes. You can use the Foundry CLI to deploy your SuperRepo from any CI system of your choice.
Object types defined in Ontology-as-code are backed by the datasources declared in your code definitions, and a stream can be one of them. Review Object with custom datasources ↗ for the definition syntax.
Can I use media sets with my Ontology and application?
Yes. You can use media sets by defining a property with type: mediaReference.