feat: expose TLSConfig for config api

[sekfung]

What this PR does:
expose TLSConfig for config api

Which issue(s) this PR fixes:
Fixes #

You should pay attention to items below to ensure your pr passes our ci test
We do not merge pr with ci tests failed

• All ut passed (run 'go test ./...' in project root)
• After go-fmt ed , run 'go fmt project' using goland.
• Golangci-lint passed, run 'sudo golangci-lint run' in project root.
• Your new-created file needs to have apache license at the top, like other existed file does.
• All integration test passed. You can run integration test locally (with docker env). Clone our dubbo-go-samples project and replace the go.mod to your dubbo-go, and run 'sudo sh start_integration_test.sh' at root of samples project root. (M1 Slice is not Support)

[justxuewei]

It seems that a TLS test fails. Please check and fix it.

[sekfung]

OK, I will fix it

[sekfung]

@justxuewei hi, plz review the changes when you are free, thx

[justxuewei]

It looks like your commits modify tons of comments, why? What formatting tools are you using? Plus, please add an Apache header for config/tls_config_test.go.

[sekfung]

1. go fmt ./... and import-formatter. That is incredible, the prev commit has passed the format check

2. I will add the license header

[justxuewei]

The comments have been heavily modified, which is unrelated to this pull request's topic, so we need to revert them back. I'll run formatting tools on my local environment to investigate what's causing the issue. Is your go version 1.20?

[sekfung]

yes, go version 1.20

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[sekfung]

Unable to load X509 Key Pair open /home/runner/work/dubbo-go-samples/dubbo-go-samples/tls/x509/client1_cert.pem: no such file or directory

It seems that the cert file path was not correct

Does the CI workflow work correctly? I had not changed the logic which read cert. Just expose tls config for config api

Other PR has the same error Unable to load X509 Key Pair

[justxuewei]

Unable to load X509 Key Pair open /home/runner/work/dubbo-go-samples/dubbo-go-samples/tls/x509/client1_cert.pem: no such file or directory

It seems that the cert file path was not correct

Does the CI workflow work correctly? I had not changed the logic which read cert. Just expose tls config for config api

Other PR has the same error Unable to load X509 Key Pair

The directory for certificates is hard-coded. It works for the integrated tests of dubbo-go-sample, but it does not work for dubbo-go. I'll let you know if it is fixed.

[sekfung]

Unable to load X509 Key Pair open /home/runner/work/dubbo-go-samples/dubbo-go-samples/tls/x509/client1_cert.pem: no such file or directory

It seems that the cert file path was not correct
Does the CI workflow work correctly? I had not changed the logic which read cert. Just expose tls config for config api
Other PR has the same error Unable to load X509 Key Pair

The directory for certificates is hard-coded. It works for the integrated tests of dubbo-go-sample, but it does not work for dubbo-go. I'll let you know if it is fixed.

ok, thx for your kindness

[justxuewei]

Lgtm, thanks @sekfung!

[justxuewei]

@AlexStocks @zhaoyunxing92 PTAL