apache / apache/incubator-seata

Synchronize inconsistent configuration items

Open
#7,465 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
26k
Forks
8.8k
Avg merge
1d 8h
Merged PRs (30d)
4

Description

### Why you need it?

There are many sources for seata configuration: JVM startup parameters, environment variables, seata configuration files, springboot configuration files, configuration center

During development, if you need to add configuration items, you need to synchronize:
- Two 'example' configuration files under `server/resources` (server-side configuration)
- Add configuration items to the corresponding class of the `spring-autoconfigure` module (for springboot project configuration loading)
- A series of configuration template files in the script directory

Current problems:
1. Some configuration items **have not been synchronized** with all configuration template files, resulting in some configurations being vague to developers and users

2. Many configuration items **have not been synchronized** to the `additional-spring-configuration-metadata.json` file of the `spring-autoconfigure` module, resulting in the lack of configuration completion function for springboot project users in the IDE

### How it could be?

If I understand these configuration templates correctly, we need to synchronize these inconsistent configurations

### Other related information

_No response_

Contributor guide

Open the contributing guide

Research direction

Compare the two example configuration files under server/resources, the spring-autoconfigure configuration classes, the additional-spring-configuration-metadata.json file, and the configuration templates in the script directory. Identify items that differ across these locations, then verify that the server, Spring Boot loading, templates, and IDE metadata are synchronized.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
backend, developer-experience
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.