Fix config schema alignment with openclaw #30
+1
−4
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.
Summary
Three fixes to align nix-clawbot with the openclaw config schema:
byProvider → byChannel: Queue config was using
messages.queue.byProviderbut openclaw expectsmessages.queue.byChanneltelegram → channels.telegram: Telegram config was generated at root level but openclaw expects it under
channels.telegramgateway.auth.tokenFile: Added new option to inject gateway auth token from a file at activation time, supporting proper secret management
Fixes
Changes
byProvidertobyChannelin option definitions andmkRoutingConfigmkTelegramConfigto generatechannels.telegraminstead of root-leveltelegramgateway.auth.tokenFileoption at both global and instance levelsmoltbotGatewayAuthactivation step to inject token from fileTest plan
byChannelinstead ofbyProviderchannels.telegraminstead of root-leveltelegram🤖 Generated with Claude Code