You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think what you are describing is not a defect in zenpacklib, but rather its expected behavior:
as described in https://zenpack-sdk.zenoss.com/en/latest/, the intent of zenpacklib is to allow you to build new ZenPacks entirely in YAML, with no need (in most cases) to write any Python code.
Thus, by design, the "zenpacklib.Device" device class does not know anything about LVM components: these components are not defined in zenpacklib, they are defined in the Linux device class.
If your ActiveMQ devices are always Linux devices, and you always want to include all the relations and datasources of a normal Linux (SSH) device... then I think you can accomplish that by how you define the base class. I..e., by defining a new device class (e.g., "ActiveMQDevice"?), and setting its base to the Linux device class, I think you inherit all the Linux device relations/datasources/etc... and then you can use the YAML to add any additional relations, etc.
So for example, if you wish to create a new ActiveMQ device class (named "ActiveMQDevice") that "inherits" all the relations of a Linux device, I think you could do something like:
The volumeGroups relationships are missing from a zenpacklib.device.
The text was updated successfully, but these errors were encountered: