-
Notifications
You must be signed in to change notification settings - Fork 59
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
Update sample to dotnet 8, use simplified API, simplify authentication #62
base: main
Are you sure you want to change the base?
Changes from 10 commits
5405b39
ed91bff
96fa56c
bb5ecb7
236be80
940be99
e09e745
51d7a27
b6a6c00
2e3f9cb
524688a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
This file was deleted.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
This file was deleted.
This file was deleted.
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,4 @@ | ||
@page | ||
@model PrivacyModel | ||
@{ | ||
ViewData["Title"] = "Privacy Policy"; | ||
} | ||
|
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.
Let's revert all of these renames and stick with current names
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 would prefer to, but I don't know how when using DotNets option pattern., do you have any advice?
I could revert the configuration integration and just parse it myself in the options class, if that is preferable?
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.
Let's revert it for now and keep it simple
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.
Can I suggest an upgrade?
In the fork we have removed all auth options, and only retained AzureDefaultCredentials... What do you think about the same here, but also only checking if
KEDA_SERVICEBUS_CONNECTION_STRING
is used, and if so, only using that?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.
btw, that was my last question, if you still want to retain the original features, I'll get right on it :)