-
Notifications
You must be signed in to change notification settings - Fork 230
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
ipatrust: fix range_type and test enhancement. #810
Merged
Merged
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
This was referenced Apr 13, 2022
Trust add with range_type worked as expected.
|
As the task is expected to fail, the AD realm name was modified to show the expected behavior more clearly.
varunmylaraiah
approved these changes
Apr 26, 2022
This patch applies several changes to the ipatrust test playbook: * Add externally defined parameters so execution in local trust environments can be configured. The available parameters are: * winserver_admin_password: the Administrator password for the AD server (default: 'SomeW1Npassword') * winserver_domain: the AD server domain (default: 'windows.local') * winserver realm: the AD server realm (by default, the uppercase version of winserver_domain) * ipaserver_domain: the FreeIPA server domain (default: 'ipa.test') * ipaserver_realm: the FreeIPA server realm (by default, the uppercase version of ipaserver_domain * Modify trust verification to check for the existence of the trust as it the output of `ipa trust-find`, instead of cheking for the number of items returned, as the number might vary. * Add idempotency tests by re-executing tasks and verifying that no change was performed. * Added tests to verify creation of trusts with different 'range_type'. * Use a Kerberos cache for shell scripts, and destroy it on exit. * Properly remove all `idrange` that might be created upon setting up a trust.
The ipatrust module was ignoring the value of `range_type`, which is required to allow for different types of idranges.
rjeffman
force-pushed
the
ipatrust_fix_range_type
branch
from
April 26, 2022 17:44
d1d37b0
to
766cf5a
Compare
t-woerner
approved these changes
Apr 27, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
While implementing
ipaidrange
module, it was found thatipatrust
support forrange_type
was missing.This PR fixes support for attribute
range_type
inipatrust
and improves test coverage and execution for this module.
Please, see individual commits for detailed changes.