-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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: Server does not start via CLI when auth
option is set
#8669
fix: Server does not start via CLI when auth
option is set
#8669
Conversation
Thanks for opening this pull request! |
@FransGH please try this one out:
|
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## release-5.x.x #8669 +/- ##
==============================================
Coverage 94.12% 94.12%
==============================================
Files 183 183
Lines 13798 13803 +5
==============================================
+ Hits 12987 12992 +5
Misses 811 811
☔ View full report in Codecov by Sentry. |
Just deployed Thanks Daniel for addressing this so quickly :) |
Thanks for reviewing @FransGH! |
@dblythy could you please add the fix to the PR description, and also a link to the alpha branch PR (if there is one)? Thanks! |
Sorry, the alpha PR is #8666 |
@mtrezza not the most important but the problem is that the server fails to start via CLI when auth is configured (as opposed to just auth-adapters not loading) |
Thanks for pointing this out, the PR title will be the changelog entry, so it's important we get this right. The server fails to start via CLI when auth is configured as a CLI parameter? If so, how about this title:
|
I didn't try via --auth, only via a config.json. Assume however that it's independent of where the CLI gets the config from. Config file, cmd parameters and env-variables should have the same checks. |
So you were using a config file and were passing that via the CLI? |
Yes, but only on staging and production. During dev a server instance is started via API where apparently the config is not so strictly checked. |
Got it, different checks for CLI vs. API doesn't sound good. Do you want to open an issue to centralize the checks for config options regardless of how they are set? Sounds like a general issue. How about this:
|
Thought about opening an issue for that but don't have time at the moment to contribute in fixing it. So not sure if it makes sense creating one? |
"Fix: Server does not start via CLI when the auth option is set." |
Sure, you don't need to contribute in fixing an issue - if you only want to report it that also helps. |
auth
option is set
auth
option is setauth
option is set
@mtrezza just for my understanding, what would be the approximate timeline for seeing this in a 5.x release update? |
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.
Looks good!
## [5.5.3](5.5.2...5.5.3) (2023-06-29) ### Bug Fixes * Server does not start via CLI when `auth` option is set ([#8669](#8669)) ([601da1e](601da1e))
🎉 This change has been released in version 5.5.3 |
Pull Request
Issue
Closes: #8665
Approach
See Related: #8666.