stacklok / stacklok/toolhive-studio
[Bug] Missing secret from provider during workload installation/editing
Open
Nobody has claimed this yet.
Bug
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 24
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 91
Description
Bug Description
We can check the secret and client_secret before making the API request, in order to show a specific semantic error message
Sentry error detail that is related, but it is correctly handled in the UI
Non-Error promise rejection captured with value: failed to build workload config: failed to resolve OAuth client secret: secret not found: CLIENT_SECRET
Steps to Reproduce
No response
Expected Behavior
No response
Actual Behavior
No response
Priority
Medium
Environment
No response
Additional Context
No response
Contributor guide
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
Locate the workload installation and editing flow that builds the workload configuration and sends the API request. Check how missing secret and client_secret values are handled, then verify that a specific semantic error is shown before the request is made rather than surfacing the provider-resolution failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100