Custom function property for security scheme is ignored

When writing a definition file to convert, I want to be able to specify the function called when a bearer token is passed. To do this, I provide the x-bearerInfoFunc property in the security scheme. However, after generating the swagger.yaml, this property is ignored and the default function name is inserted instead.

Swagger-codegen version: 3.0.10

Here is the definition I am providing:

...
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      x-bearerInfoFunc: <module path>.my_controller.my_function_name
...

And this is how it is rendered in swagger.yaml:

...
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      x-bearerInfoFunc: <module path>.authorization_controller.check_bearerAuth
...

Command line used for generation:
java -jar swagger-codegen-cli-3.0.10.jar generate -i ./<module path>/swagger/definitions.yaml -l python-flask -o python-flask-server

Is this a bug/oversight, or is there a reason why this property is ignored?

Reproduce the issue with swagger-codegen 3.0.10 using the provided definition file and the python-flask generation command, then compare the security scheme in the input with the generated swagger.yaml. Done means the supplied x-bearerInfoFunc value is preserved instead of being replaced by the generated default function name; add a regression test if the relevant test location can be identified.