Weik.io

CoreSystem Configuration

Configure core system components and infrastructure services (Deprecated)

CoreSystem Configuration

Note: CoreSystem configuration is deprecated. Use the newer configuration patterns for integration services, event sources, and event channels instead.

Defines a core system component that provides infrastructure services to the platform.

Schema Properties

PropertyTypeRequiredDefaultDescription
CategorystringYes-System category (storage, messaging, database, etc.)
TypestringYes-Specific system type within the category
TitlestringNo-Human-readable title for the system
ParametersDictionary<string, object>No{}System-specific configuration parameters

YAML Examples

Storage System

apiVersion: weik.io/v1
kind: CoreSystem
metadata:
  name: azure-blob-storage
spec:
  Category: storage
  Type: azure-blob
  Title: Azure Blob Storage
  Parameters:
    ConnectionString: ${azure-storage-connection}
    ContainerName: integrations
    RetryCount: 3

Database System

apiVersion: weik.io/v1
kind: CoreSystem
metadata:
  name: postgres-main
spec:
  Category: database
  Type: postgresql
  Title: Main PostgreSQL Database
  Parameters:
    Host: db.example.com
    Port: 5432
    Database: weikio
    Username: weikio_user
    Password: ${database-password}
    MaxPoolSize: 20

Messaging System

apiVersion: weik.io/v1
kind: CoreSystem
metadata:
  name: rabbitmq-broker
spec:
  Category: messaging
  Type: rabbitmq
  Title: RabbitMQ Message Broker
  Parameters:
    Host: rabbitmq.example.com
    Port: 5672
    VirtualHost: /
    Username: weikio
    Password: ${rabbitmq-password}
    AutomaticRecovery: true

Cache System

apiVersion: weik.io/v1
kind: CoreSystem
metadata:
  name: redis-cache
spec:
  Category: cache
  Type: redis
  Title: Redis Cache
  Parameters:
    Endpoint: redis.example.com:6379
    Password: ${redis-password}
    Database: 0
    ConnectTimeout: 5000
    SyncTimeout: 1000

Usage Notes

CoreSystem configurations were used to define infrastructure components that other services depend on. This pattern is deprecated in favor of more specific configuration types.

Migration Path

  • Storage systems → Use storage-specific integrations and services
  • Database systems → Use DatabaseChangeTracking or direct database connectors
  • Messaging systems → Use EventSource and EventChannel configurations
  • Cache systems → Configure caching at the API or integration level

Categories

Common system categories included:

  • storage - File storage, blob storage, S3
  • database - SQL and NoSQL databases
  • messaging - Message queues and brokers
  • cache - Caching systems
  • logging - Logging aggregators
  • monitoring - Monitoring and metrics systems

Parameters

Parameters are system-specific and depend on the Type. Common patterns:

  • Connection strings and endpoints
  • Authentication credentials (use Variables for secrets)
  • Timeouts and retry settings
  • Pool sizes and resource limits
  • Feature flags and options

Deprecation Notice

While CoreSystem configurations are still supported for backward compatibility, new implementations should use:

  • EventSource for event-driven systems
  • EventChannel for message routing
  • IntegrationService for custom services
  • DatabaseChangeTracking for database monitoring
  • Integration-specific parameters in flow configurations