I am creating a new integration, and for that I copied the pyproject.toml file from an existing integration. To generate the uv.lock file, I am using the uv sync command as mentioned in the Content Hub install and build steps.
Once the uv.lock file is created, I use the mp build --integration <integration_name> command to generate the build, and I can see the output in the Out folder. After that, I change IsCustom to true, generate the ZIP file, and try to install it. However, I encounter an error. Upon investigation, I found that the issue is related to dependencies.
I had some working integrations on my instance. I exported those integrations and copied it’s dependences and replaced them in the Out folder, and after doing that, the installation worked.
To reproduce this issue, I tried generating a build for an already available integration in Content Hub (InfobloxNIOS). First, I ran the build command to generate the build and installed it on my instance, and it worked correctly. Then, I removed the uv.lock file and generated it again. After that, I encountered the same issue, even though this integration is already available in the marketplace.
It seems that when we generate a new uv.lock file from the pyproject.toml file, it is not generating a valid uv.lock and is missing some dependencies, which is causing the issue. This problem also occurs with already published integrations.
I have already created two other integrations earlier and submitted them to Content Hub by following all the required steps and best practices. At that time, I did not face this issue, and everything worked as expected. I suspect that something may have broken in the new Content Hub release, or please let me know if I am doing something wrong.
I also tried using the direct build command, where the
uv.lockfile was auto-generated, but I still faced the same issue.
Any feedback is appreciated.
Thanks.
