Greenstand/treetracker-query-api

Add distribution channels to query api

Open

#311 opened on May 16, 2023

View on GitHubContributor guide
 (8 comments) (0 reactions) (1 assignee)TypeScript (65 forks)auto 404
devopsgood first issue

Repository metrics

Stars
 (17 stars)
PR merge metrics
 (PR metrics pending)

Description

We need to work on different branches and deploy these branches to different channle/domain, so we can test them, use them for different roadmaps in the whole platform, in specific:

  • Create denormalized branch and deploy this branch to alpha channel, it could be https://dev-k8s.treetracker.org/alpha/query, given our major channel is: https://dev-k8s.treetracker.org/query

Please refer to our implementation of similar workflow in the web map client: https://github.com/Greenstand/treetracker-web-map-client/blob/cwm/.releaserc.json

Contributor guide

Research direction
Study the existing .releaserc.json configuration in the web map client repository (https://github.com/Greenstand/treetracker web map client/blob/cwm/.releaserc.json). Understand how it defines branches and distribution channels. Then, in the treetracker query api repository, create a similar configuration to enable deployment of the 'denormalized' branch to the 'alpha' channel. This likely involves setting up a CI pipeline (e.g., GitHub Actions) that triggers on the new branch and deploys to a specific Kubernetes namespace or domain.
Tech stack
typescriptgithub actionskubernetes
Domain
devops
Issue type
DevOps
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitCI/CD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65