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

chore: Revise the default NATS Server address logic #420

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

joonas
Copy link
Member

@joonas joonas commented Sep 19, 2024

Feature or Problem

As it turns out, 127.0.0.1:4222 isn't a terribly helpful default.

Instead, the most common scenario we see today is one where wadm is installed in the same namespace as the NATS Servers running in the cluster, so we should simply attempt to use that address instead.

This behavior can still be overridden as before, by providing a value via wadm.config.nats.server

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

@joonas joonas requested a review from a team as a code owner September 19, 2024 02:10
@joonas joonas force-pushed the chore/default-nats-address branch 3 times, most recently from 367e705 to ef69ebf Compare September 19, 2024 03:04
Signed-off-by: Joonas Bergius <joonas@cosmonic.com>
@joonas joonas merged commit 5ea118e into wasmCloud:main Sep 19, 2024
6 checks passed
@joonas joonas deleted the chore/default-nats-address branch September 19, 2024 13:35
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.

3 participants