Closed agrare closed 2 years ago
Hey @gberginc I wonder if you guys could test this out as I don't have access to an intersight provider? Thanks!
Sure @agrare .
I got error when checking authentication using command authentication_check
on the provider, blocking also the other functionalities since credentials aren't verified:
From the rails console, get this error if it helps additionally:
Ah thanks @tjazsch that is because the existing verify_provider_credentials method is self.
in the mixin and not in the ClassMethods
section, will move it to the right place
Sure. Will be able test code again in 90 minutes if there will be any further commits.
Okay moved into the ClassMethods
section and I am able to verify (unsuccessfully, but for successful reasons :laughing:)
Sorry for the later response than expected. All functionalities this refactoring touches look good @agrare !
So I tried the following operations on the provider. All were executed successfully:
ems.authentication_check
through rails console)ems.refresh
)bundle exec rake app:spec:models
from the provider. I'm on OSX, it may differ on other systems)Nevertheless, @gberginc still needs to approve the PR.
That's awesome thanks for the testing @tjazsch really appreciate it
Thank you for doing the refactoring 😎. Appreciated.
Rather than setting
IntersightClient::Configuration.@@default
we can initialize aIntersightClient::Configuration
object, set the key and key_id, and build anIntersightClient::ApiClient
based on thatFixes https://github.com/ManageIQ/manageiq-providers-cisco_intersight/issues/44