Conversation
bfdcd43 to
2fd7276
Compare
71ce03e to
4cf96ac
Compare
ddfec69 to
eb1df00
Compare
| - name: Enable iop | ||
| if: matrix.iop == 'enabled' | ||
| run: | | ||
| ./foremanctl deploy --add-feature iop |
There was a problem hiding this comment.
calls to foremanctl deploy are expensive (adds ca 2 minutes to the execution), so I wonder if it'd be smarter to have fewer of those "add optional feature" steps and use something like {{ matrix.iop == 'enabled' && '--add-feature iop' || '' }} inside an existing step
a200e68 to
ffcfc02
Compare
|
@evgeni For now, I want to keep the same behavior of not supporting remote database yet. Looking at Obsah, I don't think that's possible but I wanted you to check me on that. I need to forbid:
|
d5bfe6f to
1b2bf3f
Compare
That's correct, today we can only forbid "if param P has value Y you can't set params A and B at all" You could add a |
I could... just less clear then when do we do parameter validation at the CLI level and when do we do it at the checks level. |
|
Sure, yeah. We could easily enhance obsah to reject things like "if A=1 then B can't be 2", but in your case you need "if A=1 then 2 cant be IN B", and I'm not sure how to nicely express that in metadata |
|
Here is my attempt to implement that structure: theforeman/obsah#104 |
95c8203 to
acbe14a
Compare
pablomh
left a comment
There was a problem hiding this comment.
Builds and creates running services :)
Signed-off-by: Eric D. Helms <ericdhelms@gmail.com>
e96e49f to
c333fd0
Compare
|
I'll need theforeman/puppet-certs#505 to get in so that installer certificate testing can pass. |
85f7f48 to
2e42420
Compare
Signed-off-by: Eric D. Helms <ericdhelms@gmail.com>
Signed-off-by: Eric D. Helms <ericdhelms@gmail.com>
Signed-off-by: Eric D. Helms <ericdhelms@gmail.com>
Signed-off-by: Eric D. Helms <ericdhelms@gmail.com>
No description provided.