feat(push): print Standby URL when actor.json.usesStandbyMode is true#1259
Draft
DaveHanns wants to merge 1 commit into
Draft
feat(push): print Standby URL when actor.json.usesStandbyMode is true#1259DaveHanns wants to merge 1 commit into
DaveHanns wants to merge 1 commit into
Conversation
When pushing an Actor that opts into Standby mode via `.actor/actor.json` (`usesStandbyMode: true`), append the public Standby endpoint to the push summary alongside the Actor URL and Build URL, and expose it as `actor.standbyUrl` in `--json` output. Before this change, callers who just pushed a Standby Actor had no signal that a Standby endpoint exists, and had to either open the Console UI or guess the host format. The public host is deterministic — `https://<username>--<name>.apify.actor` — so we can compute it directly from the Actor record we already fetched. The line is only emitted when `usesStandbyMode` is set locally, so non-Standby pushes are unaffected. Surfaced during an evaluation of Apify surfaces for agent-driven Actor development. Co-Authored-By: Claude Opus 4.7 <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
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
When pushing an Actor with
usesStandbyMode: truein.actor/actor.json, print the public Standby endpoint alongside the Actor URL and Build URL, and expose it asactor.standbyUrlin--jsonoutput.Rationale
Standby Actors are reachable at a deterministic host:
Today
apify pushprints only the Console-side Actor URL and Build URL:After enabling Standby locally there's no signal from the CLI that a public HTTP endpoint even exists — callers have to open the Console UI, or guess the
<user>--<actor>.apify.actorhost format. That's especially painful for automation / scripts that push then immediately want tocurlthe standby endpoint.Change
In
src/commands/actors/push.ts, after the build resolves:actorConfig.usesStandbyModeis truthy, computehttps://${actor.username}--${actor.name}.apify.actorfrom the Actor record we already fetched.Standby URL: <url>to the plaintext push summary (right afterBuild URL).actor.standbyUrlin the--jsonresult payload (optional field, only present when Standby is enabled locally).Non-Standby pushes are unaffected — no extra line, no new JSON key.
Example output
Before, for a Standby Actor:
After:
Test plan
apify pushon an Actor with.actor/actor.json.usesStandbyMode = trueprintsStandby URL: https://<username>--<name>.apify.actorafterBuild URL:.apify push --jsonon the same Actor emitsactor.standbyUrlwith the same value.apify pushon an Actor withoutusesStandbyModeprints noStandby URL:line and noactor.standbyUrlkey in JSON output.Surfaced during an evaluation of Apify surfaces for agent-driven Actor development.