Fargate default diff fix, logs --follow for arrays, register --rev#12
Merged
Conversation
- diff: a FARGATE definition registered without
fargatePlatformConfiguration comes back with {platformVersion:
"LATEST"} — stop reporting that server-filled default as a change
(it made every deploy register a new revision)
- logs --follow on an array parent id now attaches the same rich tail
as run --array: per-child colored prefixes, progress bar, paging;
without --follow the error points at --follow or <job-id>:<index>
- register --rev N registers a copy of existing revision N as the new
latest (roll-forward complement to rollback); works with --dry-run
- run/logs polling interval is injectable (App.poll) so the array tail
is testable without real sleeps
- README (en/ja): document --command= form for dash-leading arguments
(--command -u parses -u as a flag), plus the new flags
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Swap register --rev (copy roll-forward) for deregister --rev N: deregister exactly the given revision(s) instead of --keep-count pruning. Every target must be ACTIVE — a typo'd or already-INACTIVE revision fails the whole batch before anything is deregistered. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Four user-reported items:
1. FARGATE definitions without
fargatePlatformConfigurationalways diffed as changedRegistering a FARGATE definition without
fargatePlatformConfigurationmakes AWS fill in{platformVersion: "LATEST"}, so the nextdiff/deploynever matched the local file again — every deploy registered a new revision.computeDiffnow drops that server-filled default when the local file omits the field; an explicitly pinned version (local or remote) still compares normally.2.
logs --followon an array parent gets the rich taillogs <array-parent-id> --follownow attaches the same view asrun --array: every child interleaved behind a colored per-child prefix, progress bar, and paging beyond 32 children. Works mid-run and as a replay after completion. Without--followthe error message points at--followor<job-id>:<index>.3.
deregister --rev N— one-shot deregister of specific revisionsDeregisters exactly the given revision(s) (repeatable / comma-separated) instead of
--keep-countpruning. Every target must currently be ACTIVE: a typo'd or already-INACTIVE revision fails the whole batch before anything is deregistered. Mutually exclusive with--keep-count/--keep-revision.4. README documents the
--command=formbatchkoi run --command -uparses-uas a flag; arguments that start with a dash need--command=-u. Verified against the binary and documented in both READMEs.Also: the run/logs polling interval is injectable (
App.poll), so the array tail path is covered by tests without real sleeps.🤖 Generated with Claude Code