Sign up to take part
Registered users can ask their own questions, contribute to discussions, and be part of the Community!
Added on September 23, 2020 9:02AM
Likes: 0
Replies: 5
Hi all,
I am writing a plugin that requires an additional package, I have added it to requirements.txt file in plugins "spec" folder and rebuilt the environment several times, but this package is still not showing up in the environment - is there an additional step I need to take to force it through?
Thanks,
Ben
yes, code envs for plugins are immutable so during dev you'll need to create one for each iteration of the required packages
Hi,
if after the addition of the package you created new code envs from the plugin's Summary tab, and still don't have the package in the new code envs, as can be checked in the 'installed packages' tab of the code env in Administration > Code envs, can you attach the files from under 'code-env' in your plugin?
That makes sense, thank you for clarifying!
Does that mean - if we are updating the plugin & it needs new packages, we need to create a new code environment for plugin?