OPSAPS-46858 Fix API version for 5.15.0 #74
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
pip installation for cm-api client is failing after CM API client was updated in 5.15.0 to v20. This appears to be due to incorrect upload of python egg package to external pypi. For 5.15, there was no API version bump to v20, no new API endpoints added/modified/deleted. However there were changes to argument classes for missing fields mainly for BDR. OPSAPS-46448. Historically we appear to be bumping up CM API version every release which wasn't the case for 5.15. For customers to get more recent version of cm-api python package from external pypi we'll need to bump up the version to like 19.1.0 to avoid confusion with CM API version. The version here is simply cm-api python package version. There are more problems. Since the internal starship/cm_api repo was updated to version v30 for cdep and internal consumption that has made it's way into external cm_api repository. This change fixes it. This change will go directly to external cm_api repository. Tests: - sudo python ./setup.py install (From cm_api/python directory) Copying cm_api-19.1.0-py2.7.egg to /usr/local/lib/python2.7/dist-packages Adding cm-api 19.1.0 to easy-install.pth file Installing cmps script to /usr/local/bin Installed /usr/local/lib/python2.7/dist-packages/cm_api-19.1.0-py2.7.egg Processing dependencies for cm-api==19.1.0 Finished processing dependencies for cm-api==19.1.0
|
LGTM |
1 similar comment
|
LGTM |
cloudera-hudson
force-pushed
the
cm5-5.15.0
branch
from
ebb22f6
to
01a0026
Compare
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.
pip installation for cm-api client is failing
after CM API client was updated in 5.15.0 to v20.
This appears to be due to incorrect upload
of python egg package to external pypi.
For 5.15, there was no API version bump to v20, no new API endpoints
added/modified/deleted. However there were changes to argument classes
for missing fields mainly for BDR. OPSAPS-46448.
Historically we appear to be bumping up CM API version every release
which wasn't the case for 5.15.
For customers to get more recent version of cm-api
python package from external pypi we'll need to bump up the version to
like 19.1.0 to avoid confusion with CM API version. The version here is
simply cm-api python package version.
There are more problems.
Since the internal starship/cm_api repo was updated to version v30 for
cdep and internal consumption that has made it's way into external
cm_api repository. This change fixes it.
This change will go directly to external cm_api repository.
Tests:
Copying cm_api-19.1.0-py2.7.egg to
/usr/local/lib/python2.7/dist-packages
Adding cm-api 19.1.0 to easy-install.pth file
Installing cmps script to /usr/local/bin
Installed /usr/local/lib/python2.7/dist-packages/cm_api-19.1.0-py2.7.egg
Processing dependencies for cm-api==19.1.0
Finished processing dependencies for cm-api==19.1.0