Business Search - Technical Setup to PROD
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
This epic is to cover the following decisions and infrastructure tasks.
Decisions needed to finalize architecture diagram:
- [ ] Can all or portions of OrgBook be used in this project? (Data sources, APIs,, UI components, Solr setup tips, et c.)
- it would take 2 weeks to get OrgBook setup
- **Decision** Use suggestor setup as a reference, but implement our own
- [ ] Will this app run in OpenShift or GCP?
- *Decision* GCP
- [ ] If OpenShift, which namespaces will host which services?
- [ ] Confirm plan to know application health status
- [ ] Borrow preferred front and back end test apparatus from other team(s)
The list below should be discussed by devs, revised then made into stories.
- [ ] UI project setup
- setup project with vue 3 and vuetify 3 beta
- configure router, linting + jest tests
- grab config file / set values, route to dashboard (empty page for now)
- setup base css / other asset files
- figure out and implement auth flow (i.e. authentication redirect etc.)
- add sbc header/footer/system banner and sbc signin/signout/login pieces
- setup basic error framework (similar to ppr)
- implement sentry? (will we have our own sentry space for this?)
- implement launch darkly (will we have our own ld space for this?)
- [x] #11827
- create basic flask project setup similar to other projects with alembic, pytest, makefile, sqlalchemy model, and RESTful structure
- decide on what we will store in the search DB and build the model
- add health / version endpoints
- setup DB in GCP
- setup api in GCP
- connect to solr
- sentry?
- launch darkly?
- [ ] solr setup
- decide on new cores or new project setup in GCP or just add new index to existing
- build new index for search
- add new fields / calls (depends on 1st bullet) to existing solr integration pieces (adds / updates / deletes)
- [ ] API publishing project setup
- [ ] KeyCloak / auth flow setup
- [ ] Make project/section in 1pass for search UI and api
- [ ] CI / CD scripts
- UI
- api
- solr (if setting up our own project)
- [ ] Others as needed
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the listed architecture decisions and the completed #11827 backend setup. Then examine the remaining UI, Solr, authentication, API publishing, secrets, and CI/CD tasks and split them into stories with clear ownership. Done means the decisions are resolved and the required infrastructure work is implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, javascript, kubernetes, postgres, python, sqlalchemy
- Domain
- api, authentication, backend, ci-cd, cloud, database, devops, frontend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100