feat(scheduler): display jobLogId from scheduler start API response#27
Merged
feat(scheduler): display jobLogId from scheduler start API response#27
Conversation
Support the new jobLogId field added in codelibs/fess#3103. When a scheduler is started and job logging is enabled, the API now returns a pre-generated job log ID. Display it in text output so users can track job execution. JSON/YAML output already includes it via raw response dump. Backward compatible with older Fess versions.
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
1 participant
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
Support the new
jobLogIdfield added in codelibs/fess#3103. When a scheduler is started via the CLI, the pre-generated job log ID is now displayed in text output, allowing users to track job execution.Changes Made
src/fessctl/commands/scheduler.py: ExtractjobLogIdfrom the scheduler start API response and append it to the success message in text output when presenttests/unit/test_scheduler_start.py(new): 5 unit tests covering jobLogId present, absent (old Fess), null (logging disabled), JSON output, and error casestests/unit/test_client.py: Updated mock response intest_start_schedulerto includejobLogIdTesting
uv run pytest tests/unit/ -v)jobLogIdfield produce identical output to beforeBreaking Changes
None. The change is purely additive.
Additional Notes
jobLogIdvia raw response dump — no changes neededjobLogIdisnull(logging disabled) or absent (old Fess), the text output remains unchanged