When to Use Custom Providers
Use custom providers when you need to sync:- Internal infrastructure management systems
- Custom cloud platforms
- Database clusters
- Edge devices
- Any resource not covered by built-in providers
Using the API
Create or Update a Resource
Delete a Resource
List Resources
Using the Node.js SDK
Using a Shell Script
Using Python
Resource Schema
| Field | Required | Description |
|---|---|---|
identifier | Yes | Unique identifier for the resource |
name | Yes | Human-readable name |
kind | Yes | Resource type (use Category/Type format) |
version | Yes | Resource version/schema version |
metadata | No | Key-value pairs for filtering |
config | No | Configuration data for job agents |
Kind Naming Convention
Use a consistent naming convention:Metadata vs Config
- Metadata: Used for environment selectors and filtering
- Config: Passed to job agents for deployment execution
Running Continuously
Kubernetes CronJob
Kubernetes Deployment
Best Practices
Use Stable Identifiers
Use identifiers that won’t change:Include Essential Metadata
Include metadata for effective targeting:Handle Deletions
Remove resources that no longer exist:Next Steps
Selectors
Learn selector syntax
Environments
Create dynamic environments
API Reference
Full API documentation
Node SDK
Node.js SDK reference