pingcap / pingcap/tidb-operator
Migrate charts repo
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Now, we use the QiNiu object storage to store charts. And we need to migrate it to AWS or Github.
Ref: #4681
Is your feature request related to a problem? Please describe:
Describe the feature you'd like:
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the chart-storage implementation and referenced issue #4681, then determine whether AWS or GitHub is the intended destination; done means the charts no longer use QiNiu storage and the migration path is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github, go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100