ci/cd: Deploy Azure-based instances in a continuous manner
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
Following an initial deployment of services to Azure (https://github.com/kernelci/dashboard/issues/6), this task focuses on automating this process:
- [ ] Build images for dashboard components in GH action
- [ ] Convert Azure deployment into GH action
- [x] Bind `staging` instance to push events to `main` branch
- [ ] Bind production instance to `release-*`/`deploy-*` tags or a manual confirmation
Contributor guide
Research direction
Start by tracing the existing Azure deployment from the initial deployment referenced in issue #6, then inspect how GitHub Actions can build dashboard component images and perform the deployment. Verify that staging follows pushes to main, while production follows release-* or deploy-* tags or requires manual confirmation. Done means all unchecked deployment automation tasks are implemented and the staging and production triggers behave as specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions, python
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100