docs: fix incorrect retention-cleanup monitoring command - #61
Merged
Conversation
WORKERS.md documented 'doctl apps logs <app-id> --component retention-cleanup --type run' -- verified against the actual doctl help output that --component is not a real flag (component name is a positional argument), and confirmed by live testing against production that a SCHEDULED job with no invocations yet errors without an explicit --job-invocation ID (unlike PRE_DEPLOY jobs, which default to the current deployment's run). Corrected to the two-step sequence that actually works: list-job- invocations to find the invocation ID, then apps logs with --job-invocation. Verified the corrected first step's command shape against the live migrate job, which has actually run.
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
WORKERS.md documented
doctl apps logs <app-id> --component retention-cleanup --type runas the monitoring command —--componentis not a real flag (verified againstdoctl apps logs --help); component name is a positional argument. Additionally, for aSCHEDULEDjob with no invocations yet, the plain command errors (websocket: close 1011 internal server error) since it isn't tied to "current deployment" the wayPRE_DEPLOYjobs are.Corrects the docs to the actual working two-step sequence:
list-job-invocationsto find the invocation ID, thenapps logs ... --job-invocation <id>. Verified the log-fetch step's command shape against the livemigratejob, which has actually run.Documentation only — no code, migration, or infrastructure change.
Test plan
🤖 Generated with Claude Code