Skip to content

Fix bridge task in dev mode when entrypoint/command is defined#6707

Merged
vimtor merged 1 commit intoanomalyco:devfrom
achadha235:dev
Apr 10, 2026
Merged

Fix bridge task in dev mode when entrypoint/command is defined#6707
vimtor merged 1 commit intoanomalyco:devfrom
achadha235:dev

Conversation

@achadha235
Copy link
Copy Markdown
Contributor

@achadha235 achadha235 commented Apr 9, 2026

Problem: Currently, if you define a task with either command and / or entrypoint and run sst dev, the bridge task definition is created incorrectly with the custom command. This prevents the bridge main from being executed and the task does not work.

Screenshot 2026-04-10 at 12 39 11 AM

Expected Behavior: When a bridge task is created in dev, we should always get /app/main as the command in the task definition so that the tunneling / forwarding functionality works.

Fix: The cause was the spread operator in v[0] in /aws/task.ts. Added code to ensure command and entrypoint are not passed on in dev mode.

Copy link
Copy Markdown
Collaborator

@vimtor vimtor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for your contribution @achadha235

@vimtor vimtor changed the title Fix: Ensure bridge task main is called correctly in dev Fix bridge task in dev mode when entrypoint/command is defined Apr 10, 2026
@vimtor vimtor merged commit 9aa9aac into anomalyco:dev Apr 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants