pulp / pulp/analytics.pulpproject.org
Move analytics.proto to its own repo and allow it to be a python dependency instead of checked in code
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 5
- Avg merge
- 2h 4m
- Merged PRs (30d)
- 8
Description
Right now the built analaytics.proto is built and then checked in to both this repo and pulpcore. It should instead be consumed as a python module that is received via PyPI.
To do this:
- The analytics.proto should be moved to its own repo.
- That repo should have CI that builds the protobuf python bindings
- Publish the build bindings to PyPI via a date-based string
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
Start by locating the checked-in analytics.proto and generated Python bindings in this repository and pulpcore, then review how the bindings are currently built and consumed. Define the separate repository and its CI and PyPI publication flow; done means both consumers receive the generated module as a date-versioned Python dependency rather than checked-in code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100