-
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
Drop support for oVirt /api, always use /ovirt-engine/api #14469
Drop support for oVirt /api, always use /ovirt-engine/api #14469
Conversation
@borod108 @masayag @pkliczewski @durandom please review. |
Note that the relevant changes are only in the |
@miq-bot add-labels bug providers/rhevm |
@jhernand Cannot apply the following label because they are not recognized: bug providers/rhevm |
Addressed the Rubcop issues and the offending string issues. |
This pull request is not mergeable. Please rebase and repush. |
This pull request is not mergeable. Please rebase and repush. |
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.
code wise LGTM
@oourfali is this fine/yes ?
And I guess you have full oversight of the supported version implications, because reading the attached BZ lost me somehow :)
@@ -10,6 +10,8 @@ module ManageIQ::Providers::Redhat::InfraManager::ApiIntegration | |||
process_api_features_support | |||
end | |||
|
|||
DEFAULT_PATH = '/ovirt-engine/api'.freeze |
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.
is this used somewhere else than below? If not, I would just inline it (put the string where it's used)
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.
It isn't used anywhere else. I will inline it.
Removed the |
Note that this should be |
Versions of oVirt 3.4 and older only supported the /api path for access to the API. Since version 3.5 /ovirt-engine/api is supported as well, and /api is deprecated. In version 4.0 /api was removed completely. The provider has supported both paths, which caused confusion and problems during upgrades. As we no longer need to support oVirt 3.4 or older, that support can now be removed. That is what this patch does. The path will be still saved to the 'path' column of the 'endpoints' table, but not used at all. https://bugzilla.redhat.com/1427653
Checked commit https://github.com/jhernand/manageiq/commit/543846bf888a5acc0eec7595dd517e5458f11727 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
LGTM. |
@miq-bot assign @blomquisg @blomquisg please merge |
…rt_paths Drop support for oVirt /api, always use /ovirt-engine/api (cherry picked from commit ac8b311)
Fine backport details:
|
Yes @simaishi , I am preparing the backport. |
Backported to Euwe via #14786 |
Versions of oVirt 3.4 and older only supported the /api path for access to the
API. Since version 3.5 /ovirt-engine/api is supported as well, and /api is
deprecated. In version 4.0 /api was removed completely. The provider has
supported both paths, which caused confusion and problems during upgrades. As
we no longer need to support oVirt 3.4 or older, that support can now be
removed. That is what this patch does. The path will be still saved to the
'path' column of the 'endpoints' table, but not used at all.
https://bugzilla.redhat.com/1427653