Make schema registration optional (default: off)#399
Merged
Conversation
Add `register_schema` flag to control whether JSON schemas are generated and registered alongside task definitions. Defaults to False so task registration doesn't require schema registry support on the server. Configurable at multiple levels with clear precedence: per-worker env > global env (conductor.worker.all) > decorator > Configuration > default (False) - Add `register_schema` param to `@worker_task` and `@WorkerTask` decorators - Add `register_schema` param to `Configuration` class - Add `CONDUCTOR_REGISTER_SCHEMAS` env var for global control - Add per-worker env var: `conductor.worker.<name>.register_schema` - Gate schema generation/registration in both sync and async task runners - Update existing tests, add new tests for all config levels Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
shaileshpadave
approved these changes
Apr 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
register_schemaflag to control whether JSON schemas are generated and registered alongside task definitions. Defaults to False so task registration doesn't require schema registry support on the server.Configurable at multiple levels with clear precedence:
per-worker env > global env (conductor.worker.all) > decorator > Configuration > default (False)
register_schemaparam to@worker_taskand@WorkerTaskdecoratorsregister_schemaparam toConfigurationclassCONDUCTOR_REGISTER_SCHEMASenv var for global controlconductor.worker.<name>.register_schema