-
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
Fix seq trailing slash, respect cancellation token, make SeqOptions.ApiKey nullable #1304
Conversation
test/HealthChecks.Publisher.Seq.Tests/Functional/SeqPublisherTests.cs
Outdated
Show resolved
Hide resolved
@@ -6,7 +6,7 @@ public class SeqOptions | |||
{ | |||
public string Endpoint { get; set; } = null!; | |||
|
|||
public string ApiKey { get; set; } = null!; | |||
public string? ApiKey { get; set; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had a look at the official API client for seq and it seems that the ApiKey
can be null so it probably makes sense for it to be null here too?
https://github.com/datalust/seq-api/blob/dev/src/Seq.Api/Client/SeqApiClient.cs#L75=
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
@@ -9,12 +9,11 @@ public void add_healthcheck_when_properly_configured() | |||
services | |||
.AddHealthChecks() | |||
.AddSeqPublisher(setup => | |||
new SeqOptions() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 funny test fix
Co-authored-by: Ivan Maximov <sungam3r@yandex.ru>
What this PR does / why we need it:
SeqOptions
SeqOptions.ApiKey
is now nullable to handle cases where no api key is requiredseq_publisher_registration_should.add_healthcheck_when_properly_configured
options configured incorrectlyWhich issue(s) this PR fixes:
#1171
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
No
Please make sure you've completed the relevant tasks for this PR, out of the following list: