Skip to content

fix(nats): Validate StorageType and pin NATS test endpoint (follow-up to #10028)#10176

Merged
ReubenBond merged 2 commits into
dotnet:mainfrom
Cluster7ck:feat/nats-storage-type-validation
Jun 8, 2026
Merged

fix(nats): Validate StorageType and pin NATS test endpoint (follow-up to #10028)#10176
ReubenBond merged 2 commits into
dotnet:mainfrom
Cluster7ck:feat/nats-storage-type-validation

Conversation

@Cluster7ck

@Cluster7ck Cluster7ck commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #10028, addressing review comments.

Changes

  1. NatsStreamOptionsValidator now rejects undefined StreamConfigStorage enum values.

  2. Use NatsTestConstants.NatsClientOptions to align with existing tests.

@Cluster7ck Cluster7ck marked this pull request as ready for review June 4, 2026 09:06
@Cluster7ck Cluster7ck force-pushed the feat/nats-storage-type-validation branch from cac3308 to f7247b2 Compare June 4, 2026 10:30
Reject StorageType values that are not defined StreamConfigStorage enum
members before they reach JetStream, throwing OrleansConfigurationException
with the valid values (File/Memory). Addresses review feedback on dotnet#10028.
Addresses PR dotnet#10028 review: use NatsTestConstants.NatsClientOptions for
both the connection manager options and the verification connection so the
stream is created against and queried from the same pinned server endpoint.
@Cluster7ck Cluster7ck force-pushed the feat/nats-storage-type-validation branch from f7247b2 to 652bd64 Compare June 4, 2026 10:30
@Cluster7ck Cluster7ck changed the title Validate StorageType and pin NATS test endpoint (follow-up to #10028) fix(nats): Validate StorageType and pin NATS test endpoint (follow-up to #10028) Jun 4, 2026
@ReubenBond ReubenBond added this pull request to the merge queue Jun 8, 2026
Merged via the queue into dotnet:main with commit 70ffd6e Jun 8, 2026
62 checks passed
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.

2 participants