Uplift to swagger-codegen version 3.3.3

[seaneagan]

swagger-codegen v3.3.3:

https://github.com/OpenAPITools/openapi-generator/releases/tag/v3.3.3

added this fix:

OpenAPITools/openapi-generator#1387

which should fix #411 at least in cases where no async calls are made.

this also would address #684.

/cc @007 @micw523

[micw523]

I would be very careful to make this switch. As you see, the repo you mentioned is not swagger-codegen, but is called OpenApi generator. The repo is maintained by the original codegen authors.

The original codegen repo is now owned by Smartbear and I don’t know if k8s clients have received support from them. It’s difficult to say whether we could make the switch or not. It would be a little more feasible if the original repo contains the bug fix.

[seaneagan]

I see, I guess that's this PR that is needed then: swagger-api/swagger-codegen#8061

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.