GCP Credentials: Improved input fields
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- gcp, typescript
Research direction
No files or tests are named. Start by locating the Kaapi console's GCP credential input flow and tracing how the current JSON is accepted and sent to the backend. Identify the four existing credential fields, then verify that assembled credentials handle private-key newlines and no longer produce a 422 JSONDecodeError.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
Malformed GCP credential JSON leads to a 422 JSONDecodeError. This creates a poor user experience and could cause frustration when users encounter this issue.
Describe the solution you'd like
Collect the four GCP fields as discrete input fields in the Kaapi console:
- Add discrete input fields for the four GCP credential fields
- Assemble and store the JSON on the backend
Original issue
Context
Malformed GCP credential JSON (particularly newline escaping in the private key) produces a 422 JSONDecodeError. This is poor UX but deferred for now, as it is unlikely to be hit near-term.
Preferred long-term fix
Collect the four GCP fields as discrete input fields in the Kaapi console, so we control assembly and storage on our backend rather than relying on clients to paste well-formed JSON.
Next steps
- Add discrete input fields for the four GCP credential fields in the Kaapi console
- Assemble and store the JSON on the backend
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 4
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.
More from ProjectTech4DevAI/kaapi-frontend
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ProjectTech4DevAI/kaapi-frontend#266 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ProjectTech4DevAI/kaapi-frontend#258 · 3 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in ProjectTech4DevAI/kaapi-frontend
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·