docs: add docs about Seata configuration files #5913
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## 2.x #5913 +/- ##
============================================
+ Coverage 49.01% 49.04% +0.02%
- Complexity 4777 4783 +6
============================================
Files 913 913
Lines 31710 31710
Branches 3827 3827
============================================
+ Hits 15542 15551 +9
+ Misses 14627 14623 -4
+ Partials 1541 1536 -5 |
| username: nacos | ||
| password: nacos | ||
| # for the path of nacos health check, you need to configure an open web endpoint | ||
| context-path: /${server.servlet.context-path}/actuator |
There was a problem hiding this comment.
the default value is ${server.servlet.context-path}/actuator ? It's not a health check as I understand it.
There was a problem hiding this comment.
Thank you for your reply.
Sorry, I misunderstood. I intend to make the following changes:
username: nacos
password: nacos
# used to specify the context path in the URL, forming the complete access path, which is empty by default.
# the full URL is: :// ${server.ip}:${server.port} / ${context-path} /
# if the IP address of the server is 192.168.1.1, the port number is 7091, the context is set to /seata,
# and the client wants to initiate a request for /info, then the complete URL is as follows:
# http://192.168.1.1:7091/seata/info
context-path:
what do you think
There was a problem hiding this comment.
You can modify on this basis, and I will continue to review the modified code.
…tion center and registry
Ⅰ. Describe what this PR did
Add comments on logs and parameters related to nacos as the configuration center and registry
Ⅱ. Does this pull request fix one issue?
fixes #5608
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews