Import a project type
A new Facets control plane starts with no modules. Import an official project type to load the modules and output types for your cloud in one command, then adapt them to your organisation.
A new control plane starts empty. It ships with no IaC modules and no output types, so there is nothing yet to build a blueprint from. Importing a project type is the first thing you do after you get access.
A project type is a bundle of modules and output types imported to the control plane together. Importing one gives your organisation a working catalogue for a cloud: compute, datastores, networking, and the platform tooling around them.
Import the official project type for your cloud
Facets publishes an official project type for each cloud. Import the one you need from the console or with the Praxis CLI.
Using prompt
Import the official AWS project type and call it Production AWS.or
Using command
# See what the official library ships
raptor import project-type --list-managed
# Import the one for your cloud (--name is optional)
raptor import project-type --managed facets/aws --name "Production AWS"A managed import clones the official facets-modules-redesign repository, imports the project type with all of its modules and output types, and skips validation because the official modules are trusted. Browse the full set at facets-cloud.github.io/facets-modules-redesign.
New to the CLI? Install it first.
- Go to Ops Center and open Project Type to reach the Project Types page.
- Click Browse Templates (top right). It opens the Facets template catalogue at facets-modules-redesign, the same official set the CLI lists.
- Browse the catalogue and choose the project type you want to import.
facets/empty imports a project type with no modules. Use it when you intend to build your catalogue from scratch rather than start from the official one.
Confirm what landed
Using prompt
Show me my project types and the modules each one allows.or
Using command
raptor get project-types
raptor get resource-type-mappings "Production AWS"get resource-type-mappings lists the INTENT/FLAVOR combinations mapped to the project type, which is what you just imported. Pass whatever name the project type has, either the default or the one you gave --name.
Once you have a project, raptor get resource-types -p <project> shows which modules its blueprint can actually use. Without -p that command lists everything registered globally rather than what your import brought in.
New to the CLI? Install it first.
The imported project type appears on the Project Types page, with its Allowed Modules listed. Open it to review the modules it maps.
What to do next
- Create a project against the project type you imported, then add resources to its blueprint.
- Adapt the modules to your organisation. The imported modules are a starting point, not a fixed set: see Building a module to change one or add your own.
- Create your own project type from an existing project or type in the console: see Creating a project type.
- Import a project type from a definition you control (YAML, modules, private repos): see Import from your own definition.
Project Types
A project type is the template your projects start from: a bundle of modules, cloud settings, and guardrails that decides which modules a project can use.
Import from your own definition
Import a project type from a YAML definition you control with the Praxis CLI: the metadata format, uploading IaC modules, and importing from a private repository.