Forum Discussion

Jeff_Kinny's avatar
Jeff_Kinny
Icon for Contributor II rankContributor II
5 months ago

Having trouble re-packaging SL1 Library

Hi All, hoping someone here can help me out. I recently have been trying to make a small tweak to the python code for the out of the box silo_cisco_meraki_api Library from the Cisco: Meraki Powerpack...
Python3
  • wspearman's avatar
    wspearman
    5 months ago

    Hi Jeff!

    To answer your main question about the error and the point of that step: you can skip it. That step is for a python package you own, or a 3rd party package from the python community. In other words, it needs to be a package that pip knows about. Since silo_cisco_meraki_api is a privately hosted ScienceLogic library, pip cannot find it in the official PYPI repo.

    If you were using your own library, or one from PYPI, then that step would download any dependencies of the package so that you could include them the in the library tar bundle. Then during the collection process those dependencies would support the main package in the python virtual environment on the Collector Unit.

    In summary, you can skip the pip download step. The best thing would be to include all the dependencies that came with the original silo_cisco_meraki_api library. So during the tar step, include the python packages that came with the original. Also, don't forget to adjust the version of the new package, and include it in the Execution Environment so it gets used in place of the original.

wspearman's avatar
wspearman
Icon for Employee rankEmployee
5 months ago

Hi Jeff!

To answer your main question about the error and the point of that step: you can skip it. That step is for a python package you own, or a 3rd party package from the python community. In other words, it needs to be a package that pip knows about. Since silo_cisco_meraki_api is a privately hosted ScienceLogic library, pip cannot find it in the official PYPI repo.

If you were using your own library, or one from PYPI, then that step would download any dependencies of the package so that you could include them the in the library tar bundle. Then during the collection process those dependencies would support the main package in the python virtual environment on the Collector Unit.

In summary, you can skip the pip download step. The best thing would be to include all the dependencies that came with the original silo_cisco_meraki_api library. So during the tar step, include the python packages that came with the original. Also, don't forget to adjust the version of the new package, and include it in the Execution Environment so it gets used in place of the original.