intropy template

Authoritative reference for intropy template: inspecting the Intropy template library.

template reads the library; it renders nothing. Rendering a template into a project is intropy int create (components) or intropy sys create (the System host), and the deploy templates are rendered by intropy manifests.

The surface

intropy template list [flags]
intropy template show <template> [flags]

The template taxonomy

The official library at integrio-intropy/intropy-templates publishes eight templates in three groups: component templates (each producing a Block with a blockKind of extractor, loader, or transactional-integration), role templates (shared-library and system-host, the non-component projects of a workspace), and deploy templates (the GitOps manifest skeletons).

Template	Purpose	User-facing parameters
hello-world	ASP.NET Minimal API sample with a Dapr pub/sub trigger and a transactional send pipeline.	name
extractor	Run-to-completion extractor that sweeps a source folder and publishes each result as a CloudEvent to a pub/sub topic.	name, organization, topic, contract, empty
loader	Long-running loader that subscribes to a pub/sub topic and writes each delivered message through a destination binding.	name, organization, topic, contract, empty
transactional	Port-to-port job that polls a source folder, publishes via in-memory pub/sub, and writes the transformed result to a destination folder.	name, organization, empty
shared-contracts	Class library holding the contract types a System’s components share; scaffolded once as a sibling of the first component that declares it.	name, contract, empty
system-host	The Aspire host project of a System; declares components and edges as one typed C# declaration. Rendered by sys create with an assembled payload; without one it renders a valid empty System.	name (plus the topics, ports, components, sharedContracts values sys create assembles)
deploy-component	The workload and overlays for one Component, as one ArgoCD Application.	name, domain, system, appId, kind, workload, registry, imageNamespace, replicas, sourceDir
deploy-host	The Dapr components a System’s Components share, as one ArgoCD Application.	domain, system, pubsub, pubsubName

The empty parameter on component templates strips the sample business logic so a migration agent can fill the step bodies in. Its default differs: true for extractor and loader, false for transactional and shared-contracts.

intropy template list

List the names of the templates published in the library at the requested release. Names are accepted by template show and int create.

Flag	Description
-o, --output <format>	plain (default) or json.
--template-repo <owner/repo>	Template library on GitHub. Defaults to templateRepo from configuration, or INTROPY_TEMPLATE_REPO.
--template-version <tag>	Template release tag. Defaults to the latest release.

intropy template list

deploy-component
deploy-host
extractor
hello-world
loader
shared-contracts
system-host
transactional

intropy template show

Print a template’s manifest (metadata and parameter schema) for the requested release. --output json emits a stable, machine-readable document intended for tooling. This command replaced the removed int describe.

Flag	Description
-o, --output <format>	plain (default) or json.
--template-repo <owner/repo>	Template library on GitHub. Defaults to templateRepo from configuration, or INTROPY_TEMPLATE_REPO.
--template-version <tag>	Template release tag. Defaults to the latest release.

intropy template show hello-world --template-version v0.4.1

Dapr Minimal API (dapr-minimal-api) @ integrio-intropy/intropy-templates@v0.4.1

ASP.NET Minimal API sample with a Dapr pub/sub trigger and a transactional send pipeline.

Tags: [example dotnet dapr]

Parameters:
  * name — Project name [string]
      PascalCase identifier used for the .NET project, root namespace, and assembly. Dot-separated segments are allowed for nested namespaces (e.g. MyApi or Int1055.MyApi).
      pattern: ^[A-Z][A-Za-z0-9]*(\.[A-Z][A-Za-z0-9]*)*$
  (* = required)

Component templates additionally print what they scaffold alongside (the shared contracts dependency) and each parameter’s description, pattern, and default.

Resolution

Both commands resolve the library over the GitHub API, so --template-repo must be exactly owner/repo (URLs and SSH remotes are rejected). Unpinned, the latest GitHub release of integrio-intropy/intropy-templates is used; --template-version pins a specific release tag. Scaffolding commands record the resolved tag in the scaffold record, so a workspace’s provenance survives whichever default was current at the time.