This does not include the YAML file of the template plugin
The test case included in this repo simply tries to instantiate the element.
Perhaps the lack of a YAML file is not causing any issue at load time (are the element yaml files mandatory ? I forget off hand)... and the test does not check that any of the configuration from the default .yaml file is loaded.
To reproduce this, I compared with bst-external
.
If I run pip3 install --user .
in bst-external
, then I end up with these yaml files:
/home/tristan/.local/lib/python3.5/site-packages/bst_external/elements/flatpak_repo.yaml
/home/tristan/.local/lib/python3.5/site-packages/bst_external/elements/tar_element.yaml
/home/tristan/.local/lib/python3.5/site-packages/bst_external/elements/x86image.yaml
/home/tristan/.local/lib/python3.5/site-packages/bst_external/elements/fastboot_bootimg.yaml
/home/tristan/.local/lib/python3.5/site-packages/bst_external/elements/dpkg_deploy.yaml
/home/tristan/.local/lib/python3.5/site-packages/bst_external/elements/flatpak_image.yaml
/home/tristan/.local/lib/python3.5/site-packages/bst_external/elements/fastboot_ext4.yaml
/home/tristan/.local/lib/python3.5/site-packages/bst_external/elements/dpkg_build.yaml
But the same command in bst-plugins-template
does not add any yaml files, it does add the expected python plugin:
/home/tristan/.local/lib/python3.5/site-packages/bst_plugins_template/elements/basic_element.py