Update HTTP listening documentation#499
Merged
Merged
Conversation
|
👋 tarcisiozf, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
timothyF95
approved these changes
Jun 23, 2026
| --http-trigger-port int Port used by the local HTTP trigger server (default 2000) | ||
| --limits string Production limits to enforce during simulation: 'default' for prod defaults, path to a limits JSON file (e.g. from 'cre workflow limits export'), or 'none' to disable (default "default") | ||
| --listen Listen for HTTP requests or supported log triggers and run the simulator for each match | ||
| --listen Listen for HTTP requests or supported log triggers and run the simulator for each match (not supported by cron) |
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
2 participants
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.
This pull request adds support for configuring the HTTP trigger server port in the workflow simulator via a new CLI flag, rather than relying on a hardcoded value. The port can now be set with the
--http-trigger-portflag, and this value is propagated throughout the codebase, including tests and documentation. The default port remains 2000 if not specified.HTTP Trigger Port Configuration:
--http-trigger-port(default: 2000) to allow users to specify the port for the local HTTP trigger server insimulate.go, and updated theInputsstruct and input resolution logic to support this parameter.