Parcel fix #301
Parcel fix #301
Conversation
Parcel provides should not be hardcoded to spark-plugin as Cloudera Manager CSD files can refer to parcels based on the value set in provides.
Add a news file
|
We require contributors to sign our Contributor License Agreement and we don't have one on file for @mwies-cldr. In order for us to review and merge your code, please e-sign the Contributor License Agreement PDF. We then need to manually verify your signature, merge the PR (conda/infrastructure#861), and ping the bot to refresh the PR. |
|
@mwies-cldr Please fix the bit of lint and re-ping once the CLA has been signed. |
|
Hi there, thank you for your contribution! This pull request has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this pull request to remain open please:
NOTE: If this pull request was closed prematurely, please leave a comment. Thanks! |
Description
In the case conda-pack is being used to generate Cloudera parcel files the parcel.json file was generated with static content for the provides tag. The name spark-plugin was set here. The behavior of conda-pack was altered to set the name of the parcel in this tag. In case a CSD is being developed that needs to work together with the generated parcel they can be linked via the provides tag in the parcel : https://github.com/cloudera/cm_ext/wiki/Control-Scripts#interaction-with-parcels