Tags are not applied to plugin entities in the generated declarative config

Describe the bug When the x-kong-plugin entity is used in a spec, when generating config using one of the entry point methods (for example generateFromString, the default tag or any tags provided are not applied to the generated declarative config of the plugin.

See example in the comment below.

To Reproduce Steps to reproduce the behavior:

1. In Insomnia Designer or the inso CLI, take a spec
2. Click Generate Config or run inso generate config <spec>

Expected behavior The generated declarative config should tag the Services, Routes and plug-ins appropriately.

INS-175

[rmsy]

That clears it up, thank you!

[develohpanda]

Good eyes, and thanks for clarifying upfront @rmsy 👀

The only way to provide tags (currently) is to send them as arguments to the entry point functions in index.js. Here is some documentation showing how tags behave currently.

The original issue report overlaps another feature request - to provide tags from the spec #2682 - which is not yet accepted.

I will remove the example from the original post and move it to the related issue. That will leave my comment with the example spec and the expected output, with no tags in the input spec. In this example, the default OAS3_import tag, or any provided as an argument to, for example, generateFromString should be applied to the plugin.

Does that clear things up?