Deploy FOI-Help in a new OpenShift Environment
- Dominant language
- Python
- Stars
- 8
- Forks
- 2
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 46
Description
Title of ticket: Deploy FOI-Help in a new OpenShift Environment
#### Description
Create a brand new instance of foi-help deployment.
#### Dependencies
We need a new OpenShift environment provisioned in order to deploy to it.
Also need to determine if we're creating a new GitHub Repo (perhaps in case of them being a separate organization) or extending the existing one. The main question is about the GitHub Action CI/CD pipeline, as currently the foi-help repo deploys to the foi-help OpenShift. We could configure the one repo to deploy to multiple OpenShift environments but that might be odd, perhaps they do not wish to share their OpenShift credentails with us, in which case they would need their own GitHub repo too.
#### DOD
- [ ] "FOI" branding is made configurable (currently hard-coded to FOI)
- [ ] Deploy "foi-help" frontend+backend application to new OpenShift environment
- [ ] Configure GitHub Actions to deploy to both environments, OR clone the repo and setup it's own copied GitHub Actions (pending discussion on appropriate governance of it basically).
Contributor guide
Research direction
Start by reviewing the existing foi-help frontend and backend deployment and the repository's GitHub Actions CI/CD configuration. Resolve whether the new environment uses the existing repository or a separate one, and how credentials and governance will work. Done means configurable FOI branding, a deployment to the new environment, and an agreed pipeline setup for both environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- cloud, devops, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100