Add server certificate validation with Root CA and insecure option

[barryib]

This PR will let user validate TLS certificate with a provided root CA or choose a insecure option with no validation at all.

May solves hashicorp/terraform-provider-aws#11426 and have a lot of common usage.

Link for tests terraform-aws-modules/terraform-aws-eks#1339

[techdragon]

This would be an extremely helpful addition given the number of missing data objects in a number of the providers. (Most notably the Kubernetes provider which lacks data equivalents to almost every resource it can make) At the moment in order to work around missing Kubernetes data sources (In order to query things created with the helm provider) I have to work around the lack of TLS support by using the shell provider and using curl directly.

[barryib]

Any chance to see this PR reviewed or at least close it if it doesn't make sense here ?

[jonatan-b-kr]

Is there any current workaround while we wait for this to get merged?

[techdragon]

@jonatan-b-kr I had to use the shell provider and curl in order to get around this. Its not a very good workaround because of the limitations of the shell provider.

[barryib]

It's almost 10 months now since this PR is open without any comment from the maintainer. Is this something we want to merge in ? If yes, how can the PR be review ? If not, please tell me so I close this PR and move on another solution.

[barryib]

Maybe @apparentlymart could help ?

[barryib]

It's almost 10 months now since this PR is open without any comment from the maintainer. Is this something we want to merge in ? If yes, how can the PR be review ? If not, please tell me so I close this PR and move on another solution.

@paultyng please advise.

[barryib]

@kmoe any chance to review this PR ?

[barryib]

Maybe @aareet or @bflad can review this ? I just want to know if this something hashicorp wants to add in this provider or not.

[stevehipwell]

This would be really useful if it could be merged?

[daroga0002]

@aareet or @bflad is there chance to review this?

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

Thierno BARRY seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[sbuzonas]

@barryib perhaps this is still pending awaiting contribution attribution for the CLA

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.