GCP Migration
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2025-01-30. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1Byb2plY3QvODc0ODY)._
- [ ] DB Versioning
- [ ] Upgrade Flask to version 3 within OCP and upgrade Python version
- [ ] GCP migration
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue lists DB versioning, upgrading Flask to version 3 and Python, and migrating to GCP, but names no files, tests, or entry points. Start by locating the current database-versioning and Flask deployment configuration; completion would require all three checklist items to be addressed, though the issue does not define further acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, gcp, python
- Domain
- backend, cloud, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100