Objective
Resolve the critical mismatch where cache-memory.docker-image is defined in the JSON schema but completely missing from the Go parser implementation, making this advertised feature non-functional.
Context
The schema consistency check (discussion #3589) discovered that users can configure a custom Docker image for the cache-memory MCP server in their workflow YAML, but this configuration is silently ignored because the parser doesn't implement it.
Current State:
- Schema advertises the feature at
pkg/parser/schemas/main_workflow_schema.json:2041
- Parser struct in
pkg/workflow/cache.go:19-24 omits the DockerImage field entirely
- Users' configurations pass validation but don't work
Approach
Option A: Implement the feature (recommended if docker-image customization is needed)
- Add
DockerImage string \yaml:"docker-image,omitempty"`to theCacheMemoryEntrystruct inpkg/workflow/cache.go`
- Update the
extractCacheMemoryConfig function to handle the docker-image configuration
- Modify cache-memory MCP server generation code to use the custom image when specified
- Add validation to ensure the docker-image value is a valid image reference
Option B: Remove from schema (if feature is not intended)
- Remove the
docker-image property from the cache-memory schema definition
- Document why this feature is not supported
Files to Modify
If implementing:
pkg/workflow/cache.go - Add DockerImage field to CacheMemoryEntry struct
pkg/workflow/cache.go - Update extractCacheMemoryConfig function
pkg/workflow/mcp_servers.go - Update MCP server generation to use custom image
pkg/workflow/cache_test.go - Add test coverage for docker-image configuration
If removing:
pkg/parser/schemas/main_workflow_schema.json - Remove docker-image property from cache-memory definition
Acceptance Criteria
Related Documentation
AI generated by Plan Command for discussion #3589
Objective
Resolve the critical mismatch where
cache-memory.docker-imageis defined in the JSON schema but completely missing from the Go parser implementation, making this advertised feature non-functional.Context
The schema consistency check (discussion #3589) discovered that users can configure a custom Docker image for the cache-memory MCP server in their workflow YAML, but this configuration is silently ignored because the parser doesn't implement it.
Current State:
pkg/parser/schemas/main_workflow_schema.json:2041pkg/workflow/cache.go:19-24omits theDockerImagefield entirelyApproach
Option A: Implement the feature (recommended if docker-image customization is needed)
DockerImage string \yaml:"docker-image,omitempty"`to theCacheMemoryEntrystruct inpkg/workflow/cache.go`extractCacheMemoryConfigfunction to handle the docker-image configurationOption B: Remove from schema (if feature is not intended)
docker-imageproperty from the cache-memory schema definitionFiles to Modify
If implementing:
pkg/workflow/cache.go- Add DockerImage field to CacheMemoryEntry structpkg/workflow/cache.go- Update extractCacheMemoryConfig functionpkg/workflow/mcp_servers.go- Update MCP server generation to use custom imagepkg/workflow/cache_test.go- Add test coverage for docker-image configurationIf removing:
pkg/parser/schemas/main_workflow_schema.json- Remove docker-image property from cache-memory definitionAcceptance Criteria
Related Documentation
pkg/parser/schemas/main_workflow_schema.json:2041- Schema definitionpkg/workflow/cache.go:19-24- Current parser implementationRelated to [Schema Consistency] 🔍 Schema Consistency Check - 2025-11-11: Network & MCP Integration Analysis #3589