Catalog

Browse the resource kinds available for Platform as Code and learn how to define them in YAML.

1

Select a Resource Kind

Browse the available resource kinds grouped by category and select the resource you want to configure.

2

Review the API Version

Check the API version required by the selected resource kind.

apiVersion: platform.axio.io/v1

3

Review Dependencies

Check whether the selected resource depends on another Axio resource before creating its manifest.

4

Review Metadata and Spec Fields

Review required and optional fields, their types, and their descriptions before authoring the YAML.

5

Use the YAML Example

Use the provided example as a starting point for your Git-managed manifest.

What is the Catalog?

The Catalog contains the schema registry for every Platform as Code resource kind. It includes metadata about available fields, their types, default values, validation rules, and usage examples. Use it as a reference before authoring manifests in Git.

Resource Categories

Explore resources by category

♙ Organization ›

▣ Project ›

▤ Workspace ›

▦ Environment ›

◈ Stack ›

▣ Credentials ›

◇ Policy ›

▥ Runner ›

✣ Integration ›

... and more

Resource Schema Example

Resource Kind: Environment

Schema Example Manifest Field Reference

apiVersion: platform.axio.io/v1
kind: Environment
metadata:
  name: production
  labels:
    team: platform
spec:
  displayName: Production Environment
  workspace: production-ws
  description: Production deployment environment
  sensitive: true
  tags:
    - production

Schema Fields (Environment)

Field	Type	Required	Description
metadata.name	string	Yes	Unique name of the environment (lowercase, hyphens allowed)
spec.displayName	string	Yes	Display name for the environment
spec.workspace	string	Yes	Name of the workspace this environment belongs to
spec.description	string	No	Description of the environment
spec.sensitive	boolean	No	Marks environment as sensitive (default: false)
spec.tags	array(string)	No	List of tags for classification and filtering