-
Notifications
You must be signed in to change notification settings - Fork 898
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
Ems factory uses valid authentications #18266
Conversation
ae7d5ef
to
b6f1c39
Compare
This pull request is not mergeable. Please rebase and repush. |
The current `:authentication` factory is ambiguous. Most of the places it is used just want a valid authentication. Since the default authentication is not valid for many cases, we just stub out authentication rather than use the proper form. Any time we do not want a valid authentication, we state otherwise. I originally created an `authentication_valid` factory. But it became confusing when to use `authentication` and when to use `authentication_valid`.
cce6a36
to
f008749
Compare
Checked commits kbrock/manageiq@277544d~...f008749 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
Causes ui-classic travis failure (a PhysicalInfraManager fresh from the factory now has |
ManageIQ/manageiq#18266 changed factories by default to create "Valid" auth, requiring explicit opt-out.
The current
:authentication
factory is ambiguous.Most of the places we want to use a valid authentication.
Any time we want an invalid authentication, we state otherwise.
Unfortunately, since the default authentication is not valid for many cases, we end up stubbing out the values in our specs.
After This PR
From here, we can remove stubbing of authentication in providers [example]