Spring Boot 与 Nacos 集成：无需配置用户名和密码

一、集成 Nacos
要在 Spring Boot 项目中使用 Nacos，首先需要在项目中添加 Nacos 相关依赖。如果你使用的是 Maven，可以在 pom.xml 文件中添加以下依赖：

<dependency>
<groupId>com.alibaba.cloud</groupId>
<artifactId>spring-cloud-starter-alibaba-nacos-config</artifactId>
</dependency>
<dependency>
<groupId>com.alibaba.cloud</groupId>
<artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
</dependency>

对于 Gradle 项目，可以在 build.gradle 文件中添加以下依赖：

implementation 'com.alibaba.cloud:spring-cloud-starter-alibaba-nacos-config'
implementation 'com.alibaba.cloud:spring-cloud-starter-alibaba-nacos-discovery'

二、配置 Nacos
在 Spring Boot 项目中配置 Nacos 主要涉及两个方面：配置文件和启动配置。

1. 配置文件：在项目的 application.properties 或 application.yml 文件中添加 Nacos 相关配置。例如：

   spring.cloud.nacos.config.server-addr=127.0.0.1:8848
   spring.cloud.nacos.config.namespace=your_namespace

   或者使用 YAML 格式：

   spring:
   cloud:
   nacos:
   config:
   server-addr: 127.0.0.1:8848
   namespace: your_namespace

   这里的 server-addr 是 Nacos 服务地址，namespace 是你的 Nacos 命名空间。如果你使用的是默认设置，可以忽略这些配置。
2. 启动配置：在 Spring Boot 主类上添加 @EnableDiscoveryClient 和 @EnableConfigurationProperties(NacosConfigProperties.class) 注解，以启用 Nacos 服务发现和配置中心功能。例如：
   ```java
   import org.springframework.boot.SpringApplication;
   import org.springframework.boot.autoconfigure.SpringBootApplication;
   import org.springframework.cloud.client.discovery.EnableDiscoveryClient;
   import org.springframework.cloud.context.config.annotation.RefreshScope;
   import org.springframework.context.annotation.Bean;
   import org.springframework.context.annotation.Configuration;
   import com.alibaba.cloud.nacos.config.NacosConfigProperties;
   import com.alibaba.cloud.springcloudaliasksinaliworksnsopenfeignhystrixpalabsedgehubpalabshttpclientpalabsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzuulfilterszalarmssnsopenfeignzuulgatewayzu