Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(wash-cli)!: enable websocket port by default #1287

Merged
merged 2 commits into from
Jan 8, 2024

Conversation

brooksmtownsend
Copy link
Member

@brooksmtownsend brooksmtownsend commented Jan 8, 2024

Feature or Problem

This PR sets the NATS server launched with wash up to always listen on port 4001 for websocket connections, letting wash ui work out-of-the-box with a host launched with vanilla options.

Related Issues

N/A

Release Information

v0.26.0

Consumer Impact

Users of wash-cli will need to be aware that this opens up a websocket port for NATS to listen on that does not have TLS enabled. wash up is not the recommended tool for running in production, and for those use cases it's much better to adhere to our deployment guide to understand how to deploy NATS infrastructure.

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

This worked!

cargo run -- up -d
cargo run -- ui

Signed-off-by: Brooks Townsend <brooksmtownsend@gmail.com>
Signed-off-by: Brooks Townsend <brooksmtownsend@gmail.com>
@brooksmtownsend brooksmtownsend requested a review from a team as a code owner January 8, 2024 20:57
@brooksmtownsend brooksmtownsend enabled auto-merge (rebase) January 8, 2024 21:09
@brooksmtownsend brooksmtownsend merged commit 529136a into main Jan 8, 2024
50 checks passed
@brooksmtownsend brooksmtownsend deleted the feat/default-nats-websocket branch January 8, 2024 21:15
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.

None yet

2 participants