Bug: Config Management Overrides
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 45
- Forks
- 6
- Avg merge
- 7h 14m
- Merged PRs (30d)
- 51
Description
Lots of sharp edges with using web.runme.dev with a custom drive client and OAuth provider.
- You need to remember to do
app.disableConfigOverridesOnLoad()
-
To prevent overloading the configuration when page loads;
- We added automatic overload because the config kept changing and we wanted to push new configuration to the clients
-
Overloads/overwrites don't work as expected
- I think for some configuration we have merge behavior
- For example if the new OIDC configuration doesn't set a clientSecret but the old config did then client secret remains set to the old client secret and the OIDC login flow won't work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior in web.runme.dev with a custom drive client and OAuth provider, focusing on app.disableConfigOverridesOnLoad() and configuration overloads. Compare loading a new OIDC configuration that omits clientSecret with the existing configuration; done means overrides behave consistently and the login flow no longer retains incompatible old values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100