New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set explicit confdir option for global contexts #280
Conversation
|
For #182 |
|
You missed a few: |
|
I fixed a few. Some scripts deliberately do not have the confdir flag in bootstrap. |
|
Please explain, all of the affected scripts are server-only and thus not related to the integration effort and most probably won't work correctly with non-server configuration anyway. |
|
All bootstrap() calls without an explicit confdir argument are fine. If you think otherwise, please list all calls and give me a compelling reason to have them ignore IPA_CONFDIR. |
Some API contexts are used to modify global state (e.g. files in /etc and /var). These contexts do not support confdir overrides. Initialize the API with an explicit confdir argument to paths.ETC_IPA. The special contexts are: * backup * cli_installer * installer * ipctl * renew * restore * server * updates The patch also corrects the context of the ipa-httpd-kdcproxy script to 'server'. https://fedorahosted.org/freeipa/ticket/6389 Signed-off-by: Christian Heimes <cheimes@redhat.com>
Signed-off-by: Christian Heimes <cheimes@redhat.com>
ea2a695
to
e0d1c7f
Compare
|
|
If I understand Christian right, it is not disagreement about something which needs to be done. But rather a proposal to address rest of the scripts later in other pull request. So that we can push this PR to unblock subsequent reviews. Is it correct? If so can be proceed with checking if current code is OK and finished rest in other PR? |
|
That may be so, but why do it later when it can be done now in 10 minutes? More importantly, we try hard not to introduce new inconsistencies to our code and I don't see why this PR should be an exception (the incosistency is differing behavior of server-side scripts when IPA_CONFDIR is set, if it's not obvious). |
|
BTW, @tiran, if you don't have 10 minutes of your time to make the changes, I would be happy to spend 10 minutes of my time to amend the patch before pusing it. If that's OK with you, ACK. |
|
It's not a 10 minute change because I don't want to have a purely mechanical transition. It's going to take several hours of bike shedding and head banging. Some calls to |
|
Christian, was your answer an agreement to Honza's proposal? I.e. push this PR? Do rest later by Honza? |
|
@pvoborni No, my answer is an disagreement. Honza does not want the approve the PR as it stands now. My proposal is
|
|
Lets push this code if it is correct but only misses usecases mentioned above". Honza will implement the missing usecases in separate PR. |
|
Fixed upstream |
Some API contexts are used to modify global state (e.g. files in /etc
and /var). These contexts do not support confdir overrides. Initialize
the API with an explicit confdir argument to paths.ETC_IPA.
The special contexts are:
The patch also corrects the context of the ipa-httpd-kdcproxy script to
'server'.
https://fedorahosted.org/freeipa/ticket/6389
Signed-off-by: Christian Heimes cheimes@redhat.com