You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have a JS domain specified in your context, Jetstream requests are made to $JS.<domain>.<endpoint>. You can override the domain specified in the context using --js-domain. For example, the nats stream ls command will make a request to $JS.foo.API.STREAM.LIST when your selected context is in the foo JS domain, but if you specify --js-domain=bar, it will make the request to $JS.bar.API.STREAM.LIST. There is currently no way to achieve the standard, unspecified domain behavior when using a context that has a specified JS domain.
Expected behavior
--js-domain='' should unset the JS domain of the context for the current command.
Server and client version
Client: v0.1.2-0.20250217122005-9e54943a82b2
Host environment
Ubuntu 24.10
Steps to reproduce
Create and select a context with a Jetstream Domain specified
Try to interface with access unspecified domain endpoints ($JS.<endpoint>) using the nats stream subcommands, without selecting another context
The text was updated successfully, but these errors were encountered:
For context, the reason this is interesting to me is because I am trying to use --js-api-prefix, which I have discovered is incompatible with having a specified domain. They are incompatible because domains are a formalization of prefixes, so it doesn't make sense to have both set at the same time. This incompatibility makes being able to quickly unset the JS domain useful.
Observed behavior
When you have a JS domain specified in your context, Jetstream requests are made to
$JS.<domain>.<endpoint>
. You can override the domain specified in the context using--js-domain
. For example, thenats stream ls
command will make a request to$JS.foo.API.STREAM.LIST
when your selected context is in thefoo
JS domain, but if you specify--js-domain=bar
, it will make the request to$JS.bar.API.STREAM.LIST
. There is currently no way to achieve the standard, unspecified domain behavior when using a context that has a specified JS domain.Expected behavior
--js-domain=''
should unset the JS domain of the context for the current command.Server and client version
Client:
v0.1.2-0.20250217122005-9e54943a82b2
Host environment
Ubuntu 24.10
Steps to reproduce
$JS.<endpoint>
) using thenats stream
subcommands, without selecting another contextThe text was updated successfully, but these errors were encountered: