ProjectTech4DevAI / ProjectTech4DevAI/kaapi-guardrails
Guardrails: Redeploy to production
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 3
- Avg merge
- 9d 13h
- Merged PRs (30d)
- 2
Description
Is your feature request related to a problem?
The guardrails have not been redeployed to production since April, leaving changes only in staging. Additionally, there is a pending PII PR that has not been deployed yet.
Describe the solution you'd like
- Redeploy guardrails to production.
- Deploy the pending PII PR.
- Ensure both are integrated into the production environment.
Original issue
Context
Guardrails have not been redeployed to prod since the April sprint. In April everything (including guardrails) went to prod on the same 8 GB EC2 machine as the frontend. Since then, guardrails changes (topic relevance, b2/b3 tweaks) live only on staging. There is also a pending PII PR (Denny, ~March) not yet in prod.
Related: PR #135 (open), PR #141 (merged)
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 reviewing PR #135 and merged PR #141, then compare the current staging and production guardrails state, including the April deployment on the 8 GB EC2 machine. Done means the guardrails changes and pending PII work are both integrated and verified in production.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100