Describe the bug
apache/incubator-seata#8162
-
本人在 GitHub Actions 中要使用 Nacos，先用的是 Ubuntu 系统，使用 Docker 启动的 Nacos v3.2.3，运行正常
-
考虑到 GitHub Actions 只有 Linux（Ubuntu）才能使用 Docker，于是将 Docker 启动的 Nacos v3.2.3 修改为 直接使用 mvn spring-boot:run 运行 ，发现之前的流程完全走不通了
-
经过排查，发现 distribution 模块中的 application.properties 与 bootstrap 模块中的 application.properties 不同
- distribution 模块：用于打包成发布产物使用的模块
- bootstrap 模块：在 distribution 模块打包成发布产物所需的模块，实际运行 nacos 服务端的 jar
-
经过对比，发现核心问题出现在 nacos.core.auth.enabled 的值不同，并且发现了很多地方不同（包含提示性的注释）
-
In GitHub Actions, I need to use Nacos. Initially, I used an Ubuntu system and started Nacos v3.2.3 with Docker, which ran normally.
-
Considering that GitHub Actions only supports Docker on Linux (Ubuntu), I changed the setup from starting Nacos v3.2.3 with Docker to running it directly with mvn spring-boot:run. However, I found that the previous workflow completely failed.
-
After investigation, I discovered that the application.properties in the distribution module differs from that in the bootstrap module:
- The distribution module is used to package the release artifacts.
- The bootstrap module is the module required by the distribution module for packaging the release artifacts; it actually runs the Nacos server JAR.
-
Upon comparison, I found that the core issue lies in the different value of nacos.core.auth.enabled, and I also noticed many other differences (including hinting comments).
Expected behavior
A clear and concise description of what you expected to happen.
Actually behavior
A clear and concise description of what you actually to happen.
How to Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See errors
Desktop (please complete the following information):
- OS: [e.g. Centos]
- Version [e.g. nacos-server 1.3.1, nacos-client 1.3.1]
- Module [e.g. naming/config]
- SDK [e.g. original, spring-cloud-alibaba-nacos, dubbo]
Additional context
Add any other context about the problem here.
Describe the bug
apache/incubator-seata#8162
本人在 GitHub Actions 中要使用 Nacos，先用的是 Ubuntu 系统，使用 Docker 启动的 Nacos v3.2.3，运行正常
考虑到 GitHub Actions 只有 Linux（Ubuntu）才能使用 Docker，于是将 Docker 启动的 Nacos v3.2.3 修改为 直接使用 mvn spring-boot:run 运行 ，发现之前的流程完全走不通了
经过排查，发现 distribution 模块中的 application.properties 与 bootstrap 模块中的 application.properties 不同
经过对比，发现核心问题出现在
nacos.core.auth.enabled的值不同，并且发现了很多地方不同（包含提示性的注释）In GitHub Actions, I need to use Nacos. Initially, I used an Ubuntu system and started Nacos v3.2.3 with Docker, which ran normally.
Considering that GitHub Actions only supports Docker on Linux (Ubuntu), I changed the setup from starting Nacos v3.2.3 with Docker to running it directly with
mvn spring-boot:run. However, I found that the previous workflow completely failed.After investigation, I discovered that the
application.propertiesin the distribution module differs from that in the bootstrap module:Upon comparison, I found that the core issue lies in the different value of
nacos.core.auth.enabled, and I also noticed many other differences (including hinting comments).Expected behavior
A clear and concise description of what you expected to happen.
Actually behavior
A clear and concise description of what you actually to happen.
How to Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.