infoannouncementAtlassian calls it: Announcement
Forge CLI tunnel debugger can now be started at any host
- Announced
- APIs
- forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3305
A new --debugHost (or -d) option has been added to the Forge CLI tunnel debugger. This allows you to start the debugger at any valid IPv4 or IPv6 address, providing more flexibility for your local development environment.
What's changing
- You can now specify a custom host for the tunnel debugger using the
--debugHostor-dflag. - If no host is specified, the debugger will default to localhost (127.0.0.1).
What you need to do
- Update your Forge CLI to the latest version to access this feature.
- To start the debugger at a specific address, use the following command:
forge tunnel --debugHost <address>
- For more information on debugging Forge apps, refer to the Tunneling documentation.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.