Application program configuration management method and device, equipment, medium and product

Abstract

The invention discloses an application program configuration management method and device, equipment, a medium and a product, and relates to the technical field of financial science and technology. The method comprises the following steps: receiving initial configuration data, generating target configuration data based on the initial configuration data, and writing the target configuration data into a configuration management module; calling a dynamic environment isolation module to generate a corresponding operation environment isolation boundary, constructing a logic storage structure taking an environment type and a tenant identifier as dimensions in a configuration management module, and performing isolated storage on target configuration data according to the environment type; and in response to an automatic deployment request of a target application program, reading configuration data matched with the target deployment environment and the tenant from the logic storage structure, executing configuration validity verification before deployment, and injecting the configuration data into an application program instance in the target environment after the deployment is completed. According to the scheme, the application program can be quickly and accurately configured and managed.

Description

Technical Field

[0001] This invention relates to the field of financial technology, and in particular to a method, apparatus, device, medium, and product for configuring and managing applications. Background Technology

[0002] In modern distributed application systems, configuration management needs to simultaneously meet the requirements of isolation, dynamic update capability, and high reliability in multi-environment (e.g., development, testing, production) and multi-tenant scenarios. Traditional static configuration methods are no longer sufficient to support the needs of agile deployment and automated operation and maintenance.

[0003] Currently, a centralized configuration center is typically used to classify and store configuration data according to application or environment, and to provide configuration retrieval or push services to applications through API (Application Programming Interface). This approach is not only time-consuming but also prone to errors.

[0004] How to quickly and accurately configure and manage applications to help improve system intelligence and security is a key research topic in the industry. Summary of the Invention

[0005] This invention provides a method, apparatus, device, medium, and product for application configuration management, enabling rapid and accurate application configuration management and helping to improve system intelligence and security.

[0006] According to one aspect of the present invention, an application configuration management method is provided, the method comprising:

[0007] Receive initial configuration data, generate target configuration data based on the initial configuration data, write the target configuration data into the configuration management module, and perform version control on the target configuration data;

[0008] Based on the environment type information contained in the target configuration data, the dynamic environment isolation module is called to generate the corresponding runtime environment isolation boundary. Based on the runtime environment isolation boundary, a logical storage structure with environment type and tenant identifier as the dimensions is constructed in the configuration management module, and the target configuration data is isolated and stored according to environment type.

[0009] In response to the automated deployment request of the target application, configuration data matching the target deployment environment and tenant is read from the logical storage structure. Configuration validity is verified before deployment, and the configuration data is dynamically injected into the application instance in the target environment through a secure communication channel after deployment.

[0010] According to another aspect of the present invention, an application configuration management apparatus is provided, the apparatus comprising:

[0011] The data receiving module is used to receive initial configuration data, generate target configuration data based on the initial configuration data, write the target configuration data into the configuration management module, and perform version control on the target configuration data.

[0012] The data storage module is used to call the dynamic environment isolation module to generate the corresponding runtime environment isolation boundary based on the environment type information contained in the target configuration data, and to build a logical storage structure in the configuration management module based on the environment type and tenant identifier according to the runtime environment isolation boundary, so as to isolate and store the target configuration data according to the environment type.

[0013] The data injection module is used to respond to the automated deployment request of the target application, read configuration data that matches the target deployment environment and tenant from the logical storage structure, perform configuration validity verification before deployment, and dynamically inject the configuration data into the application instance in the target environment through a secure communication channel after deployment.

[0014] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0015] At least one processor; and

[0016] A memory that is communicatively connected to at least one processor; wherein,

[0017] The memory stores a computer program that can be executed by at least one processor, such that the at least one processor is able to execute the configuration management method of the application of any embodiment of the present invention.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, which stores computer instructions for causing a processor to execute a configuration management method for an application that implements any embodiment of the present invention.

[0019] According to another aspect of the present invention, a computer program product is provided, including a computer program that, when executed by a processor, implements a configuration management method for an application program according to any embodiment of the present invention.

[0020] The technical solution of this invention receives initial configuration data, generates target configuration data based on the initial configuration data, writes the target configuration data into the configuration management module, and performs version control on the target configuration data. Based on the environment type information contained in the target configuration data, a dynamic environment isolation module is invoked to generate a corresponding runtime environment isolation boundary. A logical storage structure based on environment type and tenant identifier is constructed in the configuration management module according to the runtime environment isolation boundary, and the target configuration data is stored in isolation according to environment type to ensure that configuration data between different environments or different tenants are invisible and do not interfere with each other. This fundamentally prevents configuration leakage and misuse across environments or tenants. Responding to the automated deployment request of the target application, configuration data matching the target deployment environment and tenant is read from the logical storage structure. Configuration validity verification is performed before deployment, and after deployment, the configuration data is dynamically injected into the application instance in the target environment through a secure communication channel. This allows for fast and accurate configuration management of applications, contributing to improved system intelligence and security.

[0021] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is a flowchart of an application configuration management method provided according to Embodiment 1 of the present invention;

[0024] Figure 2 This is a flowchart of an application configuration management method according to Embodiment 2 of the present invention;

[0025] Figure 3 This is a flowchart of an application configuration management method provided according to Embodiment 3 of the present invention;

[0026] Figure 4 This is a flowchart of an application configuration management system provided according to Embodiment 3 of the present invention.

[0027] Figure 5 This is a schematic diagram of the structure of an application configuration management device according to Embodiment 4 of the present invention;

[0028] Figure 6 This is a schematic diagram of the structure of an electronic device that implements the application configuration management method of the present invention. Detailed Implementation

[0029] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0031] Example 1

[0032] Figure 1 This is a flowchart of an application configuration management method according to Embodiment 1 of the present invention. This embodiment is applicable to situations involving application configuration management. The method can be executed by an application configuration management device (also referred to as an application configuration management system, which is not limited in this embodiment). The application configuration management device can be implemented in hardware and / or software, and can be configured in electronic devices such as computers, servers, or tablet computers. Figure 1 As shown, the method includes:

[0033] Step 110: Receive initial configuration data, generate target configuration data based on the initial configuration data, write the target configuration data into the configuration management module, and perform version control on the target configuration data.

[0034] The initial configuration data may include at least one of the following: configuration parameters, applicable environment type, and associated application identifier, etc., which are not limited in this embodiment.

[0035] Optionally, in this embodiment, initial configuration data such as configuration parameters, applicable environment types, and associated application identifiers submitted by the client or issued by the upstream system can be received. Furthermore, the received initial configuration data can be processed to obtain target configuration data. Further, the target configuration data can be written to the configuration management module, and version control can be performed on the target configuration data. Simultaneously, during the version control process, configuration change records containing version identifiers can be generated.

[0036] In this embodiment, the application's configuration management system can receive initial configuration data submitted by the client through a standardized interface. This initial configuration data can be structured data. Furthermore, the system can parse this initial configuration data and extract explicitly declared metadata fields. For example, if the applicable environment type is included, it is used to determine the target runtime context; if an associated application identifier is included, it is used to bind the configuration affiliation; if a tenant identifier is also provided, it further supports multi-tenant isolation scenarios (it is understood that in this embodiment, even if a tenant identifier is not explicitly provided, the system can fill it in by default based on the authentication context). Subsequently, the system sends the initial configuration to the configuration optimization engine, combining historical configuration versions under the same application identifier and environment type combination with the corresponding environment's runtime performance metrics (e.g., error rate, response latency) to generate intelligent configuration recommendations. The recommended values ​​are then fused with the original input according to a preset strategy to form the target configuration data. During this process, the system can also simultaneously perform format and security compliance checks (e.g., whether the port is an integer, whether it contains plaintext passwords, etc.) to ensure its deployability. After verification, the system performs atomic write in the configuration management module: assigns a globally unique version identifier (e.g., v20251106-001), persists the complete content of the target configuration data in an immutable manner, and synchronously generates a structured configuration change record. This record explicitly associates the version identifier, complete configuration content, timestamp, and application identifier, environment type, and tenant identifier extracted or derived from the initial configuration.

[0037] In one example of this embodiment, the order service of an e-commerce platform receives an initial configuration submitted by operations personnel: {"cache.ttl": 300, "environment": "production", "tenant_id": "mall_tenant"}. The system, combining historical performance data, finds a low cache hit rate and automatically optimizes cache.ttl to 600, obtaining the target configuration data. Subsequently, this configuration is written to the configuration management module, generating a configuration change record containing version identifier v20251106-001, complete configuration content, timestamp 2025-11-06T15:30:00Z, application identifier order-service, and environment and tenant information. In subsequent configuration processes, if a rollback is needed, version v20251106-001 can be precisely located and restored.

[0038] Step 120: Based on the environment type information contained in the target configuration data, call the dynamic environment isolation module to generate the corresponding runtime environment isolation boundary, and construct a logical storage structure in the configuration management module based on the environment type and tenant identifier according to the runtime environment isolation boundary, and store the target configuration data in isolation according to the environment type.

[0039] Optionally, in this embodiment, after obtaining the target configuration data, key metadata can be further extracted from the data, such as environment type and tenant identifier, which together constitute the context coordinates of the configuration's attribution. Subsequently, a pre-built dynamic environment isolation module is invoked. This module maintains an environment policy mapping table or rule engine, which can dynamically generate the corresponding runtime environment isolation boundary based on the input environment type. It should be noted that the isolation boundary involved in this embodiment is not physical network isolation, but a logical isolation abstraction. Its specific manifestation depends on the implementation of the underlying configuration management system. For example, in a key-value configuration center, it is represented by a hierarchical storage path prefix; in a cloud-native platform, it is represented by a namespace; and in a relational database, it may correspond to table partitions with combined tags.

[0040] Based on this isolation boundary, a two-dimensional logical storage structure can be dynamically constructed within the configuration management module by combining tenant identifiers. This structure can be organized according to a combination of environment type and tenant identifier. All target configuration data can be written into this logical unit, ensuring that its storage location inherently carries environment and tenant semantics.

[0041] In this embodiment, while writing the target configuration data to the logical unit, fine-grained access control policies can also be bound. For example, through the access control list mechanism of the configuration management module, only service entities with matching environment roles and correct tenant tokens in the request context can be authorized to read the data under that path. Even if an attacker knows the storage path, they cannot access it without legitimate credentials.

[0042] The advantage of this setup is that it ensures that configuration data between different environments (e.g., the production environment configuration will not be misread by the test environment) and between different tenants in the same environment (e.g., tenant A cannot see tenant B's database password), are completely isolated, invisible, and do not interfere with each other, thus helping to eliminate the risk of system failures or security leaks caused by misconfiguration or unauthorized access.

[0043] Step 130: In response to the automated deployment request of the target application, read the configuration data that matches the target deployment environment and tenant from the logical storage structure, perform configuration validity verification before deployment, and dynamically inject the configuration data into the application instance in the target environment through a secure communication channel after deployment.

[0044] The target application can be any application to be deployed, such as a financial application, a shopping application, or a reading application, etc., and is not limited to it in this embodiment.

[0045] Optionally, in this embodiment, when the system receives an automated deployment request for a target application, it can parse the target deployment environment type and tenant identifier from the request; subsequently, it can locate and read the configuration data that precisely matches it in the configuration management module to ensure that the obtained configuration is unambiguous in terms of environment and tenant dimensions.

[0046] In one optional implementation of this embodiment, before actually deploying the application instance, an isolated sandbox environment can be started to load the configuration data and perform multi-dimensional validity verification. For example, this may include syntax compliance checks, external dependency connectivity tests, or application health state simulations. The deployment process is only allowed to continue after all verification items pass. Once the application instance in the target environment has successfully started, the system dynamically injects the verified configuration data into the running instance through an encrypted secure communication channel. For example, the injection method may include calling a configuration refresh endpoint exposed by the application or writing to shared memory through a proxy.

[0047] In one example of this embodiment, a platform needs to deploy a new version of its risk control service for a tenant in a production environment. It can first initiate a deployment request. The configuration management agent then reads the corresponding configuration according to the path rules, including the database address and risk control threshold. Subsequently, it starts an image of the same version of the risk control service in an isolated container, injects the configuration, and automatically performs verification: checking the validity of the configuration format, attempting to connect to the production database with a read-only account, and calling the interface to confirm service readiness. After successful verification, the officially deployed risk control service container starts up, and the configuration management agent calls its interface through a secure channel to dynamically push the configuration to memory.

[0048] This embodiment's solution receives initial configuration data, generates target configuration data based on the initial configuration data, writes the target configuration data into the configuration management module, and performs version control on the target configuration data. Based on the environment type information contained in the target configuration data, it calls the dynamic environment isolation module to generate corresponding runtime environment isolation boundaries. Then, based on these runtime environment isolation boundaries, it constructs a logical storage structure in the configuration management module with environment type and tenant identifier as dimensions, isolating and storing the target configuration data according to environment type to ensure that configuration data between different environments or different tenants are invisible and do not interfere with each other. This fundamentally prevents configuration leakage and misuse across environments or tenants. Responding to the target application's automated deployment request, it reads configuration data matching the target deployment environment and tenant from the logical storage structure, performs configuration validity verification before deployment, and dynamically injects the configuration data into the application instance in the target environment through a secure communication channel after deployment. This allows for fast and accurate configuration management of applications, contributing to improved system intelligence and security.

[0049] Example 2

[0050] Figure 2 This is a flowchart of an application configuration management method according to Embodiment 2 of the present invention. This embodiment is a further refinement of the above technical solution, and the technical solution in this embodiment can be combined with various optional solutions in one or more of the above embodiments. Figure 2 As shown, the method includes:

[0051] Step 210: Receive initial configuration data and generate target configuration data based on the initial configuration data.

[0052] Optionally, in this embodiment, generating target configuration data based on initial configuration data may include: generating configuration recommendations based on historical configuration records and system performance indicators, and merging the configuration recommendations with the initial configuration data to generate target configuration data.

[0053] The configuration recommendation is generated by the configuration recommendation engine, which analyzes historical configuration versions, deployment success rates, system stability scores, and performance indicators based on machine learning models, and outputs configuration parameter optimization suggestions for the current environment load scenario.

[0054] In one optional implementation of this embodiment, after receiving the initial configuration data submitted by the user, it is not directly used as the final deployment configuration, but is instead input into a configuration recommendation engine driven by a machine learning model. This engine continuously collects and analyzes multi-dimensional historical data, including historical configuration versions of the same application under the same environment and tenant, the deployment success rate of the corresponding version, system stability scores (e.g., error rate, number of abnormal restarts, SLA compliance rate), and key operational performance indicators (e.g., memory usage, request latency, database connection pool saturation, etc.). Based on these time-series and correlation data, the engine identifies the potential relationship between configuration parameters and system performance through a trained supervised or reinforcement learning model, and generates personalized configuration parameter optimization suggestions (i.e., configuration recommendations) based on the actual load characteristics of the current environment (e.g., high concurrency, low latency requirements, or resource constraints).

[0055] Furthermore, the recommended configuration is integrated with the initial configuration data provided by the user according to a preset priority strategy; for example, the parameters explicitly specified by the user can be kept unchanged, and the recommended values ​​can be applied only to fields that are not specified or marked as optimizable, thereby generating target configuration data that both respects the user's intent and has been verified and optimized by the system.

[0056] The advantage of this setting is that it can prevent maintenance personnel or developers from setting unreasonable parameters due to a lack of understanding of complex systems (e.g., too small a cache or too short a timeout). It can correct or warn of potential risk parameters while preserving user intent, reduce production accidents caused by improper configuration, and significantly improve the rationality of configuration and operational performance.

[0057] Step 220: Write the target configuration data into the configuration management module and perform version control on the target configuration data to generate a configuration change record containing a version identifier.

[0058] Optionally, in this embodiment, after obtaining the target configuration data, the target configuration data can be further written into the configuration management module. After the writing is completed, version control of the target configuration data can be performed in the configuration management module to generate a configuration change record containing a version identifier.

[0059] In this embodiment, version control is performed on the target configuration data to generate a configuration change record containing a version identifier. This may include: assigning a unique version identifier to the target configuration data and storing the complete content of the target configuration data as a historical version; associating and storing the unique version identifier, complete content, timestamp, associated application identifier, and environment type to form a configuration change record.

[0060] In one optional implementation of this embodiment, after generating the target configuration data, a globally unique and monotonically ordered version identifier (e.g., a string based on a combination of timestamp and sequence number) can be assigned to it to ensure that each configuration change can be accurately referenced without conflict. Furthermore, the complete content of the target configuration data is persistently stored in the version repository of the configuration management module in an immutable manner, serving as the authoritative data source for subsequent deployment, comparison, or rollback. At the same time, a structured configuration change record can be constructed, strongly associating the unique version identifier, complete configuration content, precise timestamp at the time of writing, and metadata extracted from the initial configuration, including associated application identifier, environment type, and tenant identifier, to form a record with complete contextual semantics.

[0061] In this embodiment, by generating configuration change records, not only can efficient retrieval be supported by multiple dimensions such as application, environment, and tenant, but a reliable data foundation is also provided for subsequent effectiveness verification, automatic rollback, and compliance auditing, ensuring that the entire configuration lifecycle is traceable, reversible, and governable.

[0062] Step 230: Based on the environment type information contained in the target configuration data, call the dynamic environment isolation module to generate the corresponding runtime environment isolation boundary, and construct a logical storage structure in the configuration management module based on the environment type and tenant identifier according to the runtime environment isolation boundary, and store the target configuration data in isolation according to the environment type.

[0063] Step 240: In response to the automated deployment request of the target application, read the configuration data that matches the target deployment environment and tenant from the logical storage structure, perform configuration validity verification before deployment, and dynamically inject the configuration data into the application instance in the target environment through a secure communication channel after deployment.

[0064] Step 250: Obtain the configuration value currently used by the application instance and compare it with the injected configuration data. If they match, mark the configuration operation as successful. If they do not match, determine the most recently marked configuration version based on the configuration change record, roll back to that configuration version, and send an alarm notification.

[0065] Optionally, in this embodiment, after the configuration data is dynamically injected into the target application instance through a secure channel, the system does not assume that it has taken effect by default. Instead, it actively collects the configuration values ​​currently used by the application instance during runtime through a lightweight environment-aware agent deployed in the target environment. Furthermore, the collected actual configuration values ​​are precisely compared with the injected configuration data. If the comparison results are consistent, it indicates that the configuration has been correctly loaded and taken effect, and the status of the corresponding version can be marked as successful in the configuration change record as a trusted baseline for subsequent rollback. If an inconsistency is found, a self-healing process can be triggered: the configuration change record generated above is traversed, and the configuration version with the most recent successful status under the same application identifier, environment type, and tenant identifier is retrieved in reverse chronological order to obtain its complete configuration content. Through the same dynamic update mechanism as the injection phase, the historically successful version is re-injected into the application instance to complete the rollback. At the same time, a structured alarm notification can be generated and pushed to the operation and maintenance team through a preset channel so that the operation and maintenance team can handle the alarm information in a timely manner.

[0066] The solution in this embodiment receives initial configuration data, generates target configuration data based on the initial configuration data, writes the target configuration data into the configuration management module, performs version control on the target configuration data, and generates a configuration change record containing a version identifier. This can correct or warn of potential risk parameters while preserving user intent, reduce production accidents caused by improper configuration, and significantly improve the rationality of configuration and operational efficiency.

[0067] Example 3

[0068] Figure 3 This is a flowchart of an application configuration management method according to Embodiment 3 of the present invention. This embodiment is a further refinement of the above technical solution, and the technical solution in this embodiment can be combined with various optional solutions in one or more of the above embodiments. Figure 3 As shown, the method includes:

[0069] Step 310: Receive initial configuration data, generate target configuration data based on the initial configuration data, write the target configuration data into the configuration management module, and perform version control on the target configuration data.

[0070] Step 320: Based on the environment type information contained in the target configuration data, call the dynamic environment isolation module to generate the corresponding runtime environment isolation boundary, and construct a logical storage structure in the configuration management module based on the environment type and tenant identifier according to the runtime environment isolation boundary, and store the target configuration data in isolation according to the environment type.

[0071] Optionally, in this embodiment, based on the environment type information contained in the target configuration data, the dynamic environment isolation module is invoked to generate the corresponding runtime environment isolation boundary, and a logical storage structure based on environment type and tenant identifier is constructed in the configuration management module according to the runtime environment isolation boundary, so as to isolate and store the target configuration data according to environment type. This may include: generating a combined storage path or namespace based on environment type and tenant identifier; writing the target configuration data under the combined storage path or namespace; and applying access control policies to the combined storage path or namespace to achieve isolated storage of target configuration data according to environment type and tenant identifier.

[0072] In an optional implementation of this embodiment, after obtaining the target configuration data, the system can extract the environment type and tenant identifier, and then invoke the dynamic environment isolation module. In this embodiment, the dynamic isolation module can combine the two according to a predefined path template or naming convention to generate a unique combined storage path or namespace. Furthermore, the system writes the complete content of the target configuration data into this path or namespace, ensuring that its physical or logical affiliation is clearly bound to a specific environment and tenant.

[0073] Based on this, the system can automatically apply fine-grained access control policies to the combined storage unit; only service entities with the corresponding environment operation permissions and whose identity context matches the specified tenant are authorized to perform read or write operations.

[0074] In this embodiment, through the mechanism of path / namespace generation, data writing, and permission binding, the configuration data between different environments (e.g., production and testing) and between different tenants in the same environment (e.g., tenant A and tenant B) are completely isolated, invisible, and do not interfere with each other, effectively preventing security risks and operational failures caused by misconfiguration or unauthorized access.

[0075] Step 330: In response to the automated deployment request of the target application, read the configuration data that matches the target deployment environment and tenant from the logical storage structure, and perform configuration validity verification before deployment.

[0076] Optionally, in this embodiment, reading configuration data matching the target deployment environment and tenant from the logical storage structure and performing configuration validity verification before deployment may include: determining the storage location of the configuration data according to the target deployment environment and tenant identifier, following the same path generation rules as those used to build the logical storage structure; reading the configuration data from the storage location based on a preset access permission policy; loading the configuration data in an isolated sandbox environment and starting the corresponding version of the application container, performing configuration format compliance verification, external dependency service connectivity testing, and application health status checks; if all verification items pass, the configuration is deemed valid and allowed to proceed with the deployment process; otherwise, deployment is blocked and a verification failure alarm is generated.

[0077] In one optional implementation of this embodiment, when the automated deployment process of the target application is initiated, the precise storage location of the target configuration data in the configuration management module can be dynamically derived based on the target deployment environment type and tenant identifier explicitly specified in the deployment request, following the same path generation rules as when the logical storage structure was built earlier. This ensures that the read path and write path are semantically aligned and unambiguous. Furthermore, under the premise of satisfying the preset access permission policy, the complete configuration data is securely retrieved from this storage location. Further, the system loads the configuration in an isolated sandbox environment and starts an application container image that is completely identical to the version to be deployed, performing multi-level validity verification: for example, format compliance verification, external dependency connectivity testing, and application health status checks.

[0078] For example, format compliance verification can be performed by defining whether the configuration field exists, whether the type matches, and whether the value is within the legal range; external dependency connectivity testing can simulate the application's runtime behavior and actively probe the network reachability, authentication validity, and response correctness of databases, caches, message queues, or third-party APIs referenced in the configuration; application health status checks can call the interfaces exposed by the application within the container to confirm that it can complete initialization and enter a ready state after loading the configuration.

[0079] Furthermore, if all the above verification items pass successfully, the configuration is deemed valid, and the deployment process is allowed to continue to the actual release stage; if any verification fails, subsequent deployment operations will be immediately blocked to prevent problematic configurations from entering the production environment, and a structured alarm containing the failure type, error stack, configuration version, and suggested remedial measures will be automatically generated and pushed to the monitoring and alarm platform.

[0080] The solution in this embodiment achieves closed-loop control of configuration access by strictly locating configurations according to unified path rules based on environment type and tenant identifier before application deployment, securely reading them in conjunction with permission policies, and automatically verifying the configuration format compliance, dependency connectivity, and application health status in an isolated sandbox. This not only eliminates the risks of cross-environment and cross-tenant configuration mismatch and unauthorized access, but also intercepts problems at the release source, preventing invalid or incompatible configurations from flowing into the production environment. At the same time, it automatically generates structured alarms when verification fails, accelerating fault location and repair, and significantly improving the reliability, security, and operational efficiency of deployment.

[0081] Step 340: After deployment, dynamically inject the configuration data into the application instance in the target environment through a secure communication channel.

[0082] Optionally, in this embodiment, after the application container or process in the target environment has finished starting and entered the ready state, the previously verified complete configuration data can be pushed from the configuration management module to the application instance through an encrypted and authenticated secure communication channel. The injection process does not rely on application restart, but uses the dynamic configuration refresh interface, data encryption and integrity verification exposed by the application in advance to ensure that the configuration data is not eavesdropped, tampered with or forged during transmission, thereby achieving hot update and rapid effect of configuration while ensuring security.

[0083] Step 350: Obtain the configuration value currently used by the application instance and compare it with the injected configuration data. If they match, mark the configuration operation as successful. If they do not match, determine the most recently marked configuration version based on the configuration change record, roll back to that configuration version, and send an alarm notification.

[0084] Optionally, in this embodiment, the configuration value currently used by the application instance is obtained, and the configuration value is compared with the injected configuration data. If they match, the configuration operation is marked as successful. If they do not match, the configuration version marked as successful most recently is determined based on the configuration change record, and the configuration is rolled back to that version. At the same time, an alarm notification is sent. This may include: using an environment-aware agent deployed in the target environment to call the configuration query interface provided by the application or scan the runtime context to collect the currently effective configuration value; comparing the configuration value with the injected configuration data at the field level or hash value; if the comparison result matches, the corresponding version is marked as successful in the configuration change record; if the comparison result does not match, the configuration version marked as successful most recently under the same application identifier and environment type is retrieved in reverse chronological order in the configuration change record, and the complete configuration content corresponding to the configuration version is obtained; the rollback operation is performed through a dynamic injection mechanism, and an alarm notification containing difference information and rollback details is generated.

[0085] In an optional implementation of this embodiment, after the configuration data is dynamically injected into the target application instance through a secure channel, the system does not assume that it has successfully taken effect. Instead, a lightweight environment-aware agent deployed in the target environment actively collects the configuration values ​​currently used by the application during runtime. Furthermore, the agent precisely compares the collected actual configuration values ​​with the injected configuration data; for example, a field-by-field comparison or a strong hash value calculation for both can be used for consistency verification. If the comparison results are consistent, it indicates that the configuration has been completely and correctly loaded, and the system immediately marks the status of this version as successfully effective in the corresponding configuration change record, serving as a trusted baseline for subsequent rollback. If an inconsistency is detected, a self-healing process is immediately triggered: the configuration change record is retrieved in reverse chronological order for the most recent version with a successful activation status under the same application identifier, environment type, and tenant identifier. Its complete configuration content is obtained, and the historical version is pushed back to the application instance through the same dynamic configuration update mechanism as the injection phase, completing the automatic rollback. At the same time, the system generates a structured alarm notification, including difference details, failed version identifier, rollback target version identifier, timestamp, and suggested troubleshooting direction, and pushes it in real time through a preset channel to achieve automatic fault identification, recovery, and closed-loop alarm.

[0086] The solution in this embodiment actively collects the actual configuration values ​​during application runtime after configuration injection and compares them with the expected injected data at the field level or by hash, thus verifying whether the configuration is effective. This effectively solves the hidden risk of configuration being pushed but not loaded. Once an inconsistency is detected, the system can automatically roll back to the most recently marked trusted configuration version that has been successfully implemented under the same application, environment, and tenant, and simultaneously generate an alarm notification containing specific differences and rollback details. This significantly improves the system's reliability, observability, and autonomous operation and maintenance capabilities in complex multi-tenant and multi-environment scenarios.

[0087] Based on the above technical solutions, the application configuration management method may also include: when a code commit event is detected, performing static syntax tree analysis on the source code to detect whether there is hard-coded sensitive configuration information or production environment-specific parameters; if the detection result is that they exist, blocking the code merging process and generating a security alert.

[0088] In one optional implementation of this embodiment, when the code repository detects a code commit event, a static analysis pipeline can be automatically triggered to parse the submitted source code and construct an abstract syntax tree (AST) for its corresponding programming language, rather than relying solely on regular expressions or keyword matching. Furthermore, the AST nodes are traversed to accurately identify whether there is hard-coded sensitive configuration information or production-specific parameters. If the analysis confirms the presence of violations, the system will automatically block the code merging process, preventing problematic code from entering the main branch, and simultaneously generate a structured security alert containing the file path, line number, sensitive field type, risk level, and remediation suggestions for the violating code. This alert is then pushed to the developers and security team, thereby intercepting configuration leaks and environment coupling risks early in development, ensuring code security and deployment flexibility.

[0089] The solution in this embodiment performs deep static analysis of the source code based on an abstract syntax tree during the code submission phase. This enables accurate identification of hard-coded sensitive information and production-specific parameters, effectively avoiding false positives or false negatives caused by regular expression matching. Once violations are detected, the merging process is immediately blocked and a structured security alert is generated. This intercepts configuration security risks in the early stages of development, preventing sensitive data leakage, environment coupling, or incorrect configurations from flowing into the subsequent pipeline. This significantly improves the security, code compliance, and deployment reliability of the software supply chain.

[0090] To better understand the application configuration management method involved in this embodiment, Figure 4 This is a flowchart of an application configuration management system according to Embodiment 3 of the present invention, with reference to... Figure 4 It can include the following:

[0091] Developers define environment configuration templates (e.g., configuration templates for development, testing, and production environments) through the visual interface of the configuration management module (visual configuration management) and store them in the central configuration repository (part of the configuration management module). These configuration templates are then passed to the dynamic environment isolation module.

[0092] The dynamic environment isolation module can generate isolation boundaries based on environment definitions (ensuring that the configuration of each environment is stored and managed independently).

[0093] The configuration management module can store configuration information in a central configuration repository in isolation according to the environment (using version control tools); through the intelligent configuration recommendation submodule, it collects historical configuration data and environment status data, trains them using machine learning models (such as decision trees and random forests), and recommends the best configuration (providing suggestions when users modify or create configurations).

[0094] Quality gate checks (during code commit): Static code analysis tools can be used to check whether the code contains values ​​from configuration management modules (especially sensitive information, such as production environment configurations).

[0095] The automated deployment module can be integrated with continuous integration or continuous delivery tools to perform automated deployments (such as using blue-green deployments or rolling updates); run automated tests before deployment to ensure correct configuration; and adjust configurations (such as adjusting connection pool size) based on performance monitoring data (from environment-aware agents or monitoring systems) at runtime.

[0096] Environment-aware agents can dynamically apply configuration information to their environment (e.g., update application configuration).

[0097] The security audit module can record all configuration changes (who, when, and what was changed); monitor abnormal changes and security threats (such as unauthorized access) in real time; adjust security policies (such as restricting access) based on threat detection results; and send alarm notifications when anomalies are detected.

[0098] Multi-tenancy support, as part of the configuration management module, isolates storage and access configurations based on tenant IDs and implements access control.

[0099] Visual configuration management can display configuration information, historical changes, current status, etc. in a graphical way.

[0100] The solutions in this invention employ dynamic environment isolation to ensure that configuration information between different environments does not interfere with each other, avoiding the problem of test environments mistakenly connecting to production environments. Security audit modules and environment-aware agents ensure the security of configuration information transmission and application. Quality access control checks further prevent sensitive information from being leaked into the code repository. Adaptive security policies adjust security strategies based on system operating status and security threats, improving system security. An automated deployment module reduces the workload of manual configuration and code review, improving development and operation efficiency. Intelligent configuration recommendations help developers quickly select the best configuration, and dynamic configuration adjustments automatically optimize configurations based on system load and performance indicators. Version control and audit logs ensure the traceability of configuration information change history, facilitating problem investigation and responsibility allocation. Multi-tenancy support ensures complete isolation of configuration information between different tenants, and visual configuration management provides an intuitive management and monitoring interface. Automation and centralized management reduce human error and improve the consistency and accuracy of configuration information.

[0101] Example 4

[0102] Figure 5 This is a schematic diagram of the structure of an application configuration management device according to Embodiment 4 of the present invention. Figure 5As shown, the device includes a data receiving module 510, a data storage module 520, and a data injection module 530.

[0103] The data receiving module 510 is used to receive initial configuration data, generate target configuration data based on the initial configuration data, write the target configuration data into the configuration management module, and perform version control on the target configuration data.

[0104] The data storage module 520 is used to call the dynamic environment isolation module to generate the corresponding runtime environment isolation boundary based on the environment type information contained in the target configuration data, and to build a logical storage structure in the configuration management module based on the environment type and tenant identifier according to the runtime environment isolation boundary, so as to isolate and store the target configuration data according to the environment type.

[0105] The data injection module 530 is used to respond to the automated deployment request of the target application, read configuration data that matches the target deployment environment and tenant from the logical storage structure, perform configuration validity verification before deployment, and dynamically inject the configuration data into the application instance in the target environment through a secure communication channel after deployment.

[0106] The solution in this embodiment receives initial configuration data through a data receiving module, generates target configuration data based on the initial configuration data, writes the target configuration data into a configuration management module, and performs version control on the target configuration data. The data storage module, based on the environment type information contained in the target configuration data, calls a dynamic environment isolation module to generate corresponding runtime environment isolation boundaries. Based on these runtime environment isolation boundaries, a logical storage structure is constructed in the configuration management module, using environment type and tenant identifier as dimensions, to isolate and store the target configuration data according to environment type, ensuring that configuration data between different environments or different tenants are invisible and do not interfere with each other. The data injection module responds to the automated deployment request of the target application, reads configuration data matching the target deployment environment and tenant from the logical storage structure, performs configuration validity verification before deployment, and dynamically injects the configuration data into the application instance in the target environment through a secure communication channel after deployment. This allows for fast and accurate configuration management of applications, contributing to improved system intelligence and security.

[0107] In an optional implementation of this embodiment, the data receiving module 510 is specifically used to generate configuration recommendations based on historical configuration records and system operating performance indicators, and to merge the configuration recommendations with the initial configuration data to generate target configuration data;

[0108] Initial configuration data includes at least one of the following: configuration parameters, applicable environment type, and associated application identifier;

[0109] The configuration recommendations are generated by the configuration recommendation engine, which analyzes historical configuration versions, deployment success rates, system stability scores, and performance metrics based on machine learning models, and outputs optimization suggestions for configuration parameters for the current environment and load scenario.

[0110] In an optional implementation of this embodiment, the data receiving module 510 is further configured to assign a unique version identifier to the target configuration data and store the complete content of the target configuration data as a historical version.

[0111] The unique version identifier, complete content, timestamp, associated application identifier, and environment type are stored together to form a configuration change record.

[0112] In an optional implementation of this embodiment, the data storage module 520 is specifically used to generate a combined storage path or namespace based on the environment type and tenant identifier;

[0113] Write the target configuration data to the combined storage path or namespace;

[0114] Apply access control policies to combined storage paths or namespaces to achieve isolated storage of target configuration data by environment type and tenant identity.

[0115] In an optional implementation of this embodiment, the data injection module 530 is specifically used to determine the storage location of the configuration data according to the target deployment environment and tenant identifier, following the same path generation rules as the construction logical storage structure;

[0116] Based on the preset access permission policy, read configuration data from the storage location;

[0117] Load configuration data in the isolated sandbox environment and start the corresponding version of the application container to perform configuration format compliance verification, external dependency service connectivity testing and application health status check;

[0118] If all verification items pass, the configuration is deemed valid and the deployment process is allowed; otherwise, the deployment is blocked and a verification failure alarm is generated.

[0119] In an optional implementation of this embodiment, the application configuration management device further includes: a configuration module, configured to obtain the configuration value currently actually used by the application instance, compare the configuration value with the injected configuration data; if the two are consistent, mark the current configuration operation as successful; if they are inconsistent, determine the configuration version that was most recently marked as successful based on the configuration change record, roll back to that configuration version, and send an alarm notification.

[0120] The configuration change record is generated during the version control process of the target configuration data, and the configuration change record contains a version identifier.

[0121] In an optional implementation of this embodiment, the configuration module is specifically used to collect the currently effective configuration values ​​by calling the configuration query interface provided by the application or scanning the runtime context through the environment-aware agent deployed in the target environment.

[0122] The configuration value is compared with the injected configuration data at the field level or by hash value.

[0123] If the comparison results are consistent, mark the corresponding version as successfully effective in the configuration change record;

[0124] If the comparison results are inconsistent, the configuration change record will be searched in reverse chronological order for the most recent configuration version marked as successfully effective under the same application identifier and environment type, and the complete configuration content corresponding to the configuration version will be obtained.

[0125] The rollback operation is performed through a dynamic injection mechanism, and an alert notification containing difference information and rollback details is generated at the same time.

[0126] In an optional implementation of this embodiment, the application configuration management device further includes: a code detection submodule, used for:

[0127] When a code commit event is detected, a static syntax tree analysis is performed on the source code to check for hard-coded sensitive configuration information or production-specific parameters. If the detection result is positive, the code merging process is blocked and a security alert is generated.

[0128] The application configuration management device provided in the embodiments of the present invention can execute the application configuration management method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0129] The collection, storage, use, processing, transmission, provision, and disclosure of configuration data involved in the technical solutions of this invention comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0130] Example 5

[0131] Figure 6A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0132] like Figure 6 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded into the RAM 13 from the storage unit 18. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0133] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0134] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as application configuration management methods.

[0135] In some embodiments, the application configuration management method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the application configuration management method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to execute the application configuration management method by any other suitable means (e.g., by means of firmware).

[0136] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0137] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0138] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, RAM, ROM, erasable programmable read-only memory (EPROM), optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0139] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device for displaying information to the user (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0140] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0141] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system. It addresses the shortcomings of traditional physical hosts and Virtual Private Servers (VPS) in terms of management difficulty and weak business scalability.

[0142] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and no limitation is imposed herein.

[0143] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

[0144] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements a database detection method as provided in any embodiment of this application.

[0145] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including LANs or WANs—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0146] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0147] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A method for configuring and managing an application, characterized in that, The method includes: Receive initial configuration data, generate target configuration data based on the initial configuration data, write the target configuration data into the configuration management module, and perform version control on the target configuration data; Based on the environment type information contained in the target configuration data, the dynamic environment isolation module is invoked to generate the corresponding runtime environment isolation boundary. Based on the runtime environment isolation boundary, a logical storage structure with environment type and tenant identifier as dimensions is constructed in the configuration management module, and the target configuration data is isolated and stored according to environment type. In response to the automated deployment request of the target application, configuration data matching the target deployment environment and tenant is read from the logical storage structure. Before deployment, configuration validity verification is performed, and after deployment, the configuration data is dynamically injected into the application instance in the target environment through a secure communication channel.

2. The application configuration management method according to claim 1, characterized in that, The process of generating target configuration data based on the initial configuration data, writing the target configuration data into the configuration management module, and performing version control on the target configuration data includes: Based on historical configuration records and system performance indicators, a configuration recommendation is generated, and the configuration recommendation is merged with the initial configuration data to generate target configuration data. The initial configuration data includes at least one of the following: configuration parameters, applicable environment type, and associated application identifier; The configuration recommendation is generated by a configuration recommendation engine, which analyzes historical configuration versions, deployment success rates, system stability scores, and performance indicators based on machine learning models, and outputs configuration parameter optimization suggestions for the current environment load scenario. Assign a unique version identifier to the target configuration data and store the complete content of the target configuration data as a historical version; The unique version identifier, the complete content, the timestamp, the associated application identifier, and the environment type are stored together to form a configuration change record.

3. The application configuration management method according to claim 1, characterized in that, The step involves, based on the environment type information contained in the target configuration data, calling the dynamic environment isolation module to generate a corresponding runtime environment isolation boundary, and constructing a logical storage structure in the configuration management module based on the environment type and tenant identifier according to the runtime environment isolation boundary, thereby isolating and storing the target configuration data according to environment type, including: Generate a combined storage path or namespace based on the environment type and the tenant identifier; Write the target configuration data to the combined storage path or namespace; Access control policies are applied to the combined storage paths or namespaces to achieve isolated storage of the target configuration data based on environment type and tenant identifier.

4. The application configuration management method according to claim 1, characterized in that, The step of reading configuration data matching the target deployment environment and tenant from the logical storage structure and performing configuration validity verification before deployment includes: Based on the target deployment environment and tenant identifier, the storage location of the configuration data is determined according to the same path generation rules used to construct the logical storage structure; Based on the preset access permission policy, configuration data is read from the storage location; Load the configuration data in the isolated sandbox environment and start the corresponding version of the application container to perform configuration format compliance verification, external dependency service connectivity testing and application health status check; If all verification items pass, the configuration is deemed valid and the deployment process is allowed; otherwise, the deployment is blocked and a verification failure alarm is generated.

5. The application configuration management method according to claim 1, characterized in that, After dynamically injecting the configuration data into the application instance in the target environment via a secure communication channel, the method further includes: Obtain the configuration value currently used by the application instance and compare it with the injected configuration data. If they match, mark the configuration operation as successful. If they do not match, determine the most recently marked configuration version as successful based on the configuration change record, roll back to that configuration version, and send an alarm notification. The configuration change record is generated during the version control process of the target configuration data, and the configuration change record contains a version identifier.

6. The application configuration management method according to claim 5, characterized in that, The step involves obtaining the configuration value currently used by the application instance and comparing it with the injected configuration data; if they match, the configuration operation is marked as successful. If there is a discrepancy, the configuration version most recently marked as successfully effective will be determined based on the configuration change record, and a rollback will be performed to that configuration version. Simultaneously, an alert notification will be sent, including: By deploying an environment-aware agent in the target environment, the application's configuration query interface is invoked or the runtime context is scanned to collect the currently effective configuration values. The configuration value is compared with the injected configuration data at the field level or by hash value. If the comparison results are consistent, mark the corresponding version as successfully effective in the configuration change record; If the comparison results are inconsistent, the configuration change record is searched in reverse chronological order for the most recent configuration version marked as successfully effective under the same application identifier and environment type, and the complete configuration content corresponding to the configuration version is obtained. The rollback operation is performed through a dynamic injection mechanism, and an alert notification containing difference information and rollback details is generated at the same time.

7. The application configuration management method according to claim 1, characterized in that, The method further includes: When a code commit event is detected, a static syntax tree analysis is performed on the source code to check for hard-coded sensitive configuration information or production-specific parameters. If the detection result is positive, the code merging process is blocked and a security alert is generated.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the configuration management method of the application according to any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the configuration management method of the application program as described in any one of claims 1-7.

10. A computer program product comprising a computer program that, when executed by a processor, implements the configuration management method of the application according to any one of claims 1-7.

Images