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.
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.
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.
No. SuperRepo does not currently support PySpark transforms. Data pipeline support is in development; review Coming in the future for the capabilities currently planned.
Yes. You can use the Foundry CLI to deploy your SuperRepo from any CI system of your choice.
No. SuperRepo does not currently support compute modules.
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.
Yes. You can use media sets by defining a property with type: mediaReference.
No. The template that scaffolds your repository is a starting point only; once you create a SuperRepo, the generated files belong to your repository, and later changes to the template are not applied to it. Once created, the repository is yours to maintain: its dependencies, build configuration, and generated files.
The Foundry CLI is upgraded separately and can update itself to the latest version:
Copied!1foundry update self