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
Integration-snmp was bumped to v4.0.2 and published on 2024-05-20, Monday, and was picked up for the Versioned Plugin Reference (VPR).
@karenzone kicked off a LSR docgen job. The job completed successfully, but it didn't pick up any changes.
This message in the output indicates that integration-snmp is getting skipped because it is tagged as non-default integration. (You can see the same messaging for integration-zeromq, which we DO NOT want getting picked up at this time.
It appears that we have two other non-default integration plugins.
It seems weird that the other two non-default plugins are being picked up for the docgen job, but they aren't mentioned in the skiplist. So obviously, there's some way to get plugins building that I'm not aware of. Can we figure out what that is, and then perhaps add those two in-process plugins to the skiplist with default-plugins: false and "skip-list": true? And then change docs tooling to allow non-default integration plugins such as integration-snmp is in the interim?
The text was updated successfully, but these errors were encountered:
UPDATE: The root cause still exists, but this particular issue was resolved when integration-snmp became a default plugin with the merge of elastic/logstash#16180.
Integration-snmp docs are not being picked up in LSR docgen.
Some context
integration-snmp
is getting skipped because it is tagged asnon-default
integration. (You can see the same messaging forintegration-zeromq
, which we DO NOT want getting picked up at this time.How do we want to handle this?
default-plugins: false
and"skip-list": true
? And then change docs tooling to allow non-default integration plugins such asintegration-snmp
is in the interim?The text was updated successfully, but these errors were encountered: