Plugin extension 'enabled' not respected in OpenAPI config

To Reproduce

Add a plugin extension similar to the following to an OAI spec:

      x-kong-plugin-cors:
        enabled: false
        config:
          origins: 
            - "*"
          credentials: false
          preflight_continue: false

Then run inso generate config path/to/file.yml. Type is not important, as both output formats have the same issue.

Expected

Since enabled: false is present, it would either be present and disabled or not present in the generated output at all.

Actual

The same output is generated, regardless of whether enabled is true or false.

[HarryET]

Unfortunately I’m not at a computer right now but I can send one through in the next 24h!

That would be awesome, thanks. I’ll try make one myself but if that fails ill wait for yours 😃

[Tieske]

since this is a valid property for Kong, I think it should be valid to set it in the OAS doc as well. Which then results in the plugin being added to the generated config, with the property set to false.

My 2cts