Tagging Kong Entities in O2K

As an API designer, I would like the ability to add Kong tags and Kubernetes labels in my OpenAPI specifications. This feature should be optional when I call generateFromSpec. When I add tag elements in OAS, the openapi-2-kong library could generate Kong tags when using the kong-declarative-config type and would also generate labels when using the kong-for-kubernetes type.

When deploying with deck or k8s, I will then be able to specify tags, so I have finer grained control over the Kong configuration. An example use case is say there are keys that have been configured with the key-auth plugin which are not contained in the OAS document, when deck runs against Kong, those keys will be removed, which is an undesirable scenario.