Capsule flavor - #735
Conversation
85ba423 to
2a773f5
Compare
jeremylenz
left a comment
jeremylenz
left a comment
There was a problem hiding this comment.
Thanks @arvind4501
Looking forward to this!
| - content/ansible | ||
| - content/container | ||
| - content/rpm | ||
| - remote-execution |
There was a problem hiding this comment.
Now that templates and registration features are available, Capsule flavor should have them 🙂
There was a problem hiding this comment.
Sure we can add those, but in SAT-47662 these are not part of the enabled features by default. having said that i think we can surely enable those as they were in foreman-installer.
@ekohl what do you think about enabling these features by default in capsule deployment?
There was a problem hiding this comment.
Similar to #726 I think we should first aim at parity with the existing install where possible. I'll modify the downstream issue accordingly.
There was a problem hiding this comment.
Similar to #726 I think we should first aim at parity with the existing install where possible
does that mean, we should add those(templates, registration) feature in capsule defaults?
0fa7703 to
25334b3
Compare
25334b3 to
9207d0f
Compare
There was a problem hiding this comment.
If you put this under verndor_overrides/satellite, you only need one cp command in the setup. I've originally meant the satellite here as the product, not the software.
There was a problem hiding this comment.
Or if we decide to keep it separate we might need packaging change as similar to satellite flavor?
There was a problem hiding this comment.
we need packaging change both ways, i opted what evgeni suggested to put overrides under verndor_overrides/satellite.
There was a problem hiding this comment.
It needs a packaging change downstream either way (which Arvind already has prepared).
The files here are only for CI.
evgeni
left a comment
evgeni
left a comment
There was a problem hiding this comment.
one tests nitpick, but ack either way
Gauravtalreja1
left a comment
Gauravtalreja1
left a comment
There was a problem hiding this comment.
ACK, tested with foremanctl-3.0.0.develop-4.20260814050952506859.pr735.207.g06e3c13.el10.noarch 🍏
Scenarios tested:
- Satellite + Capsule deployment with vendor overrides -> works
- Auth bundle workflow (generate, fetch/copy, deploy-proxy) -> works
- Health check passes
- Pulp API, services, mirror mode, RHSM URL -> correct
- Feature listing correctly hides/shows enabled features
- Capsule uses auth bundle certs, no CA key present -> works
- Capsule registered on Satellite correctly, and content sync works
- No regressions on foreman-proxy-content flavor
5 participants
Why are you introducing these changes? (Problem description, related links)
What are the changes introduced in this pull request?
How to test this pull request
Steps to reproduce:
Checklist