AMBARI-25018. End users should be able to execute setup-ldap tool without manual intervention #2706
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hout manual intervention
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
rlevas
approved these changes
Dec 10, 2018
vishalsuvagia
pushed a commit
to vishalsuvagia/ambari
that referenced
this pull request
Feb 26, 2019
…hout manual intervention (apache#2706)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
We should provide a way to our end user to execute
ambari-server setup-ldapin a non-interactive way (i.e. all answers are provided by command line options).This was not the case when we wanted to setup a secure LDAP (SSL is set to true) but we did not want to use a custom trust store. In this case the following question(s) were being asked:
To address this issue I modified the tool to find out whether it's being executed in non-interactive mode or not. Non-interactive mode, in this respect, means that all properties which require a non-empty answer have their answers provided via CLI options.
How was this patch tested?
In addition to running unit tests I've executed several E2E tests within my vagrant environment; see test results in this file: setup_ldap_in_ambari_2.7.100.0-171.txt