Azure / azure-service-bus-emulator-installer

This repository acts as a central hub for handling issues, collecting feedback, and facilitating discussions related to the Azure Service Bus Emulator.
https://learn.microsoft.com/en-us/azure/service-bus-messaging/overview-emulator
MIT License
137 stars 5 forks source link

doesn't client.CreateTopicAsync supported by the emulator? #33

Open Marusyk opened 1 week ago

Marusyk commented 1 week ago

I can connect to the emulator, send/receive messages by using the code from ServiceBus.Emulator.Console.Sample

but if I add

string connectionString = "Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;";

var client = new ServiceBusAdministrationClient(connectionString);
await client.CreateTopicAsync("topic.1111111");

it says

'Retry failed after 4 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (No connection could be made because the target machine actively refused it. (localhost:443)) (No connection could be made because the target machine actively refused it. (localhost:443)) (No connection could be made because the target machine actively refused it. (localhost:443)) (No connection could be made because the target machine actively refused it. (localhost:443))'

  1. what are the limitations of the emulator? where is it described?
  2. can we only declare topics/queues in the Config.json manually? really? who needs this emulator then?
Saglodha commented 1 week ago

@Marusyk - You can find limitations in our public documentation - https://learn.microsoft.com/en-us/azure/service-bus-messaging/overview-emulator#known-limitations. Along with what's mentioned here, SQL filters and actions are also not compatible with current version.

Currently, entities can only be declared by config.json and emulator doesn't support on-fly management operations using Client side SDK.

MattHartz commented 19 hours ago

@Saglodha is this in the roadmap?