ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Credentials: Fetching AWS creds for ``/document`` endpoints
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Describe the bug
Currently, document upload and fetching related endpoints are directly accessing AWS credentials without fetching them through the organization and project-specific logic. This bypasses the necessary logic to ensure that AWS credentials are scoped by org_id and project_id.
Expected Behavior:
-
The document endpoints should fetch AWS credentials using get_provider_credential scoped by org_id and project_id.
-
If the credentials are missing or invalid, the endpoint should return a clear failure response (e.g., 400 Bad Request with a message like "AWS credentials are missing or invalid").
-
The project_id should be correctly passed in the request and used when fetching AWS credentials.
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
Start at the document upload and fetching endpoints and trace how they currently access AWS credentials. Compare that path with get_provider_credential, then verify that org_id and project_id are passed through and that missing or invalid credentials produce the specified failure response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100