stackabletech / stackabletech/docker-images
Use consistent versioning for Druid images with the authorizer plugin
Open
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 22
- Forks
- 6
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 30
Description
As a user of druid images I want to be able to use images that apply image versioning consistently. Currently we have:
0.22.1-authorizer0.1.0-stackable0
0.22.1-authorizer0.1.0-stackable0.2.0
0.22.1-stackable0
0.22.1-stackable0.1.0
where 0.22.1-stackable0 does not to resolve to 0.22.1-authorizer0.1.0-stackable0.2.0
Contributor guide
No contributing guide indexed for this repository
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 file, test, or entry point is named. Start by locating the Druid image definition and the logic that generates image tags, then compare the four version forms shown in the issue. Done means the shorter stackable tag resolves consistently with the authorizer image version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100