-
Notifications
You must be signed in to change notification settings - Fork 804
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
Add different modes for checking health on Azure Service Bus queues and subscriptions #1565
Conversation
From API diff I see that you introduced binary breaking changes. |
@marioleed I have a feeling that v7 packages will be published soon so I would do more breaking changes here, i.e. moving more properties into options class to simplify ctors. |
Co-authored-by: Ivan Maximov <sungam3r@yandex.ru>
Ah yes, I first set |
I'm waiting for review of #1574 from maintainers. After that my suggestion is - do any breaking change you want to improve public API surface/readability. |
@marioleed #1574 in master, you can move on |
@sungam3r I think I'm done. I guess I don't need to change version number as v7.0.0 already indicates a breaking change. |
test/HealthChecks.AzureServiceBus.Tests/HealthChecks.AzureServiceBus.Tests.csproj
Outdated
Show resolved
Hide resolved
src/HealthChecks.AzureServiceBus/AzureServiceBusQueueHealthCheck.cs
Outdated
Show resolved
Hide resolved
src/HealthChecks.AzureServiceBus/AzureServiceBusTopicHealthCheck.cs
Outdated
Show resolved
Hide resolved
src/HealthChecks.AzureServiceBus/AzureServiceBusTopicHealthCheck.cs
Outdated
Show resolved
Hide resolved
src/HealthChecks.AzureServiceBus/AzureServiceBusTopicHealthCheck.cs
Outdated
Show resolved
Hide resolved
src/HealthChecks.AzureServiceBus/AzureServiceBusTopicHealthCheck.cs
Outdated
Show resolved
Hide resolved
src/HealthChecks.AzureServiceBus/Configuration/AzureServiceBusHealthCheckOptions.cs
Outdated
Show resolved
Hide resolved
…HealthCheckOptions.cs
...lthChecks.AzureServiceBus/DependencyInjection/AzureServiceBusHealthCheckBuilderExtensions.cs
Outdated
Show resolved
Hide resolved
...lthChecks.AzureServiceBus/DependencyInjection/AzureServiceBusHealthCheckBuilderExtensions.cs
Outdated
Show resolved
Hide resolved
...lthChecks.AzureServiceBus/DependencyInjection/AzureServiceBusHealthCheckBuilderExtensions.cs
Outdated
Show resolved
Hide resolved
...lthChecks.AzureServiceBus/DependencyInjection/AzureServiceBusHealthCheckBuilderExtensions.cs
Outdated
Show resolved
Hide resolved
…iceBusHealthCheckBuilderExtensions.cs
…iceBusHealthCheckBuilderExtensions.cs
…iceBusHealthCheckBuilderExtensions.cs
…iceBusHealthCheckBuilderExtensions.cs
@marioleed Did you think about exposing extension metods with only options or Action<options> arguments? |
@sungam3r Yes, I thought it was sufficient with |
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## master #1565 +/- ##
===========================================
+ Coverage 13.82% 66.18% +52.35%
===========================================
Files 7 145 +138
Lines 188 3883 +3695
Branches 21 386 +365
===========================================
+ Hits 26 2570 +2544
- Misses 158 1226 +1068
- Partials 4 87 +83
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Good, generic option argument is even better, completely forgot about this. |
Thanks. Would you like me to publish previews ASAP? If not then I can do some other work here and publish all preview packages some time later. |
There's no hurry 👍 |
What this PR does / why we need it:
Adds AzureServiceBusOptions to enable different health check modes for Azure Service Bus queues and subscriptions.
Which issue(s) this PR fixes:
Please reference the issue this PR will close: #1556
Special notes for your reviewer:
This is a proposal aimed at minimal changes, hence only minor version is updated. I would have liked to add the setup action parameter before the name parameter, but that would introduce a breaking change and I feel it's not worth it at this point. However, if it's desired to re-arrange the parameters order (introducing a breaking change), then I'm fine with that too (the api would look cleaner IMHO).
I was considering an Enum for the different modes, though as you know, naming things is hard, so I used a bool rather than trying to come up with correct names for what the modes do.
Does this PR introduce a user-facing change?:
Please make sure you've completed the relevant tasks for this PR, out of the following list: