Remove the use of dynectsoap library from dyn provider since it is not licensed or actively being maintained

[jlamillan]

What would you like to be added:

Remove the use of the dynectsoap library from the dyn provider since it is not licensed or actively being maintained.

Background:

The dyn provider was updated a while back to reduce the amount of SOAP exchange boiler-code by using a library called dynectsoap.

Earlier this year, we ran into an issue that originated in the library that ultimately prevented us from using the dyn provider on our network. We submitted pull request to resolve the issue back in March, but neither the bug nor the PR have received any attention. The project shows no activity for two-years.

Forking the project also does not appear to be a viable solution since, according to GitHub's licensing help page, states that:

without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The Open Source Guide provides additional guidance on choosing the correct license for your project.

Why is this needed:

If the author of dynectsoap is not responsive to issues, PRs, and will not add a license that enables others to use and maintain it, we should remove the use of the library.

[seanmalloy]

/remove-kind feature
/kind cleanup

[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-contributor-experience at kubernetes/community.
/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-contributor-experience at kubernetes/community.
/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.

[PG2000]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@PG2000: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen
/remove-lifecycle rotten

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.