RHEL subscription-manager macro or documented pattern for self-service images
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, python
- Domain
- build-system, devops
Research direction
Start with config/image/build_secret.py and compare the existing apt.j2 and dnf.j2 package-manager macros. Review how container-generator handles the credential file, registration cleanup, and conditional CRB/EPEL behavior for RHEL 8 and 9. Done means a documented macro or pattern uses BuildSecret without embedding credentials and covers the required registration flow.
Written by the indexing model from the issue text.
Description
Problem
Self-service customers building their own images (unlike Posit's own first-party product images, which only ever target UBI — see images-shared#575) may target full subscription-gated RHEL rather than UBI. Bakery has no pattern for this today: BuildSecret (config/image/build_secret.py) is a generic mechanism for passing secrets to docker buildx build, but nothing wires it to subscription-manager register or conditional CodeReady Builder enablement.
container-generator's own approach: Red Hat credentials in a separate .pw file, copied in and deleted after registration, with conditional CRB/EPEL enablement differing between RHEL 8 and 9.
Scope
A macro (or documented pattern, if a macro is overkill for what's essentially one subscription-manager register call plus cleanup) parallel to the existing package-manager macros (apt.j2/dnf.j2), using BuildSecret for credential passing rather than embedding credentials in the Containerfile.
Non-goal
Distinct from images-shared#575's UBI work — UBI is deliberately subscription-free, so this pattern is never needed there.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 24
Getting set up
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.
More from posit-dev/images-shared
-
cvp:0 docker tdp:1
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
posit-dev/images-shared#757 · 2 comments ·
Maintainers usually reply within 1 day
-
bug cvp:0 docker priority/medium python tdp:1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
posit-dev/images-shared#685 ·
Maintainers usually reply within 1 day
-
slack-build-notify: no persisted alert state — causes suppressed repeat-failure and recovery alertsOpenbug cicd cvp:0 docker needs discussion observability tdp:2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
posit-dev/images-shared#677 ·
Maintainers usually reply within 1 day
-
cvp:0 docker tdp:2 tech debt
Difficulty 4/5 3-5 days Newbie friendliness 48/100
posit-dev/images-shared#795 ·
Maintainers usually reply within 1 day
-
cicd cvp:0 docker enhancement tdp:2
Difficulty 5/5 Over a week Newbie friendliness 35/100
posit-dev/images-shared#773 ·
Maintainers usually reply within 1 day
All issues in posit-dev/images-shared
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PedestrianDynamics/pyFDS-Evac#199 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
521xueweihan/HelloGitHub#3790 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sandialabs/atlas-ui-3#978 ·
Maintainers usually reply within 1 day
-
area: tests perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Nitjsefnie-Harness-Commons/daedalus#1255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4256 ·
Maintainers usually reply within 1 day