-
Notifications
You must be signed in to change notification settings - Fork 27
Local ActiveDirectory integration testing #61
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
Conversation
admin_user: ENV.fetch("ACTIVEDIRECTORY_USER"), | ||
admin_password: ENV.fetch("ACTIVEDIRECTORY_PASSWORD"), | ||
search_domains: ENV.fetch("ACTIVEDIRECTORY_SEARCH_DOMAINS"), | ||
instrumentation_service: @service |
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.
We might be able to make this generic using INTEGRATION_HOST
et al.
Like how this is handled considering our situation with TravisCI and AD! |
```sh | ||
$ cp test/support/vm/activedirectory/env.sh{.example,} | ||
|
||
# edit ad-env.sh and fill in with your VM's values, then |
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.
ad-env.sh
should probably be activedirectory/env.sh
right?
@jch taking this over so I can merge it and get 1.5 released. |
@jch wanna take a quick look at this to make sure it makes sense. |
…testing Local ActiveDirectory integration testing
We're unable to run ActiveDirectory in CI at this time, so I documented how to run tests against a local AD instance. I also added additional tests for the AD membership validator. Assuming a similar seed file is loaded into AD, we'll be able to run these tests locally.
cc @mtodd @jameswhite