WO2024041358A1

WO2024041358A1 - Configuration file updating method and apparatus, electronic device and readable storage medium

Info

Publication number: WO2024041358A1
Application number: PCT/CN2023/111451
Authority: WO
Inventors: 常舒超
Original assignee: 中兴通讯股份有限公司
Priority date: 2022-08-24
Filing date: 2023-08-07
Publication date: 2024-02-29
Also published as: CN117667129A

Abstract

A configuration file updating method and apparatus, an electronic device, and a readable storage medium. The method comprises: acquiring all configuration parameters in a first configuration file (S110); updating each configuration parameter according to pre-generated annotation information (S120), the annotation information being used for indicating an update strategy of each configuration parameter; and generating a second configuration file according to an update processing result (S130).

Description

Configuration file update method, device, electronic device and readable storage medium

cross reference

This application requests the priority of a Chinese patent application filed with the China Patent Office on August 24, 2022, with application number 202211016851.6 and titled "Configuration file update method, device, electronic device and readable storage medium". All the application's The contents are incorporated into this application by reference.

Technical field

This application belongs to the field of data processing technology, and specifically relates to a configuration file updating method, device, electronic equipment and readable storage medium.

Background technique

Currently, in order to better adapt to technological developments, application configuration files are upgraded more frequently or parameters are updated between versions. The main way to update the parameters of the current configuration file (which can be referred to as configuration parameters) is to only upgrade the parameters that need to be updated, without considering other parameters that do not need to be updated. This will cause some parameters to be missing in subsequent versions, which is not conducive to the follow-up. Maintenance of version parameters.

In other words, there is a problem of data loss or deletion in the relevant configuration parameter update method.

Contents of the invention

The purpose of the embodiments of the present application is to provide a configuration file updating method, device, electronic device and readable storage medium, which can solve the problem of data loss or deletion in the configuration parameter updating method of related technologies.

In a first aspect, embodiments of the present application provide a configuration file updating method, which includes: acquiring all configuration parameters in the first configuration file; updating each configuration parameter according to pre-generated annotation information, the annotation information being Instructing an update strategy for each configuration parameter; generating a second configuration file according to the result of the update process.

In a second aspect, embodiments of the present application provide a configuration file updating device. The device includes: a configuration parameter acquisition unit for acquiring all configuration parameters in the first configuration file; an update unit, configured to update each configuration parameter according to pre-generated annotation information, the annotation information being used to indicate an update strategy for each configuration parameter; a second configuration file generating unit configured to generate a third configuration file according to the result of the update process. Two configuration files.

In a third aspect, embodiments of the present application provide an electronic device. The electronic device includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor. The program or instructions are When executed by the processor, the steps of the method described in the first aspect are implemented.

In a fourth aspect, embodiments of the present application provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented. .

Description of drawings

Figure 1 is a schematic flow chart of a configuration file updating method provided by an embodiment of the present application;

Figure 2 is another schematic flowchart of a configuration file updating method provided by an embodiment of the present application;

Figure 3 is a schematic diagram of the parameter correlation range between the configuration file and update requirement information provided by the embodiment of the present application;

Figure 4 is a schematic flow chart of service configuration file parsing provided by an embodiment of the present application;

Figure 5 is an example diagram of the parsing process of service configuration file update according to the embodiment of the present application;

Figure 6 is an example flowchart of the preparation phase of service configuration file update according to the embodiment of the present application;

Figure 7 is an example flowchart of the comparison phase of service configuration file update according to the embodiment of the present application;

Figure 8 is an example flowchart of the result splicing phase of the service configuration file update according to the embodiment of the present application;

Figure 9 is a schematic structural diagram of a configuration file updating device provided by an embodiment of the present application;

Figure 10 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art fall within the scope of protection of this application.

The terms "first", "second", etc. in the description and claims of this application are used to distinguish Similar objects, rather than describing a specific order or sequence. It is to be understood that the figures so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in orders other than those illustrated or described herein, and that "first,""second," etc. are distinguished Objects are usually of one type, and the number of objects is not limited. For example, the first object can be one or multiple.

In view of the problem of data loss or deletion in the configuration parameter update method of the related art, the embodiment of the present application provides a configuration file update scheme, which processes all configuration parameters in the configuration file that need to be updated, and uses this to Each configuration parameter is updated to obtain an updated configuration file. Since all configuration parameters in the configuration file are marked, the problem of data loss or deletion in related technologies can be overcome, thereby improving the accuracy of configuration parameter update. .

The embodiments of the present application will be described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios.

Figure 1 is a schematic flowchart of a configuration file update method provided by an embodiment of the present application. The method 100 can be executed by a terminal device. In other words, the method may be executed by software or hardware installed on the terminal device. As shown in Figure 1, the method may include the following steps S110-S130.

S110: Obtain all configuration parameters in the first configuration file. The first configuration file here refers to the configuration file that needs to be updated.

S120: Update each configuration parameter according to the pre-generated annotation information. The annotation information is used to indicate the update strategy of each configuration parameter.

S130: Generate a second configuration file according to the result of the above update process.

The configuration file updating method provided by the embodiment of the present application separately updates all configuration parameters in the first configuration file according to the pre-generated annotation information, and generates a second configuration file based on the update processing results. All configuration parameters are annotated, so the problem of data loss or missingness in related technologies can be overcome, thereby improving the accuracy of configuration file updates.

In a possible implementation, annotation information may be generated based on update requirement information and all configuration parameters in the first configuration file, where the update requirement information is used to indicate configuration parameters in the second configuration file and their update requirements.

In a possible implementation, before performing the update process in S120, the above-mentioned first configuration file, annotation information, and update requirement information may be converted into a program-recognizable format to facilitate the update process.

In a possible implementation, the update strategy in step S120 may be discarding (ie, no need to appear in the second configuration file), using current values (ie, using parameter values in the first configuration file), using update value (that is, using the updated value), the union of the current value and the updated value with priority based on the current value, the union of the current value and the updated value with priority based on the updated value, etc.

The above-mentioned union of the current value and the updated value based on the current value as priority means: for a parameter (also called a parameter item), for example, the parameter type is a dictionary type (or called a dictionary value), then the current value can be is called the current list, and the updated value can be called the update list. If the values of the two lists are different, the final value is the union of the two lists. For the case where the keys are the same but the values are different, Get the value in the current list. Similarly, the union of the current value and the updated value based on the priority of the updated value means that the final value is the union of the two lists. For the case where the key (key) is the same but the value (value) is different, take Update the values in the list.

In one embodiment, when the update requirement information of a configuration parameter is discarded, when marking the configuration parameter, the update policy of the configuration parameter needs to be marked as discarded. During the update process, this configuration parameter will be deleted, that is, it will not be included in the updated second configuration file.

In a possible implementation, when each parameter (hereinafter referred to as parameter item) in the configuration file is marked respectively, the annotation information may specifically include: parameter item type, update strategy, and subsidiary parameters of the parameter item, etc. . The parameter item types here can include common types (i.e. in Table 1 Ordinary values), array types (i.e., list values in Table 1), and dictionary types (i.e., dictionary values in Table 1), etc.

Table 1 is an example of parameter item type annotation, as shown in Table 1:

Table 1

Based on the above parameter types, examples of labeling of update strategies are shown in Table 2-Table 4 below. In the following examples, the first configuration file is called origin-file, and the update requirement information is called current-file.

Table 2 is an example of the update strategy (that is, the strategy name in Table 2) annotation for common values, as shown in Table 2:

Table 2

Table 3 is an example of update strategy annotation for list values, as shown in Table 3:

table 3

Table 4 is an example of update strategy annotation for dictionary values, as shown in Table 4:

Table 4

In a possible implementation, if a parameter item is not expected to exist after an update and upgrade, it can be marked as deprecated, for example, marked as deprecated.

In a possible implementation, if the parameter item type is a list value or dictionary value, the parameter There will be some small items in the item. If you do not want some small items to still exist after the update and upgrade, you can mark them in deprecatedItem (a code name). If you want some small items in the parameter items to exist no matter what after the update and upgrade, you can mark them in comfirmItem (a code name). If some small items in the parameters are mutually exclusive and you want to retain one of the values after update and upgrade, you can mark it in mutexItem (a code name).

Table 5 is an example of small item labeling, as shown in Table 5:

table 5

In a possible implementation, the mark information (can be called mark-file) can be in a common file format to facilitate program identification and parsing. For parameter annotation, all parameters to be annotated need to be within the known range. By updating the upgrade path (lower version->higher version), all possible parameter items can be obtained.

In one example, the annotation information may be in YAML (a markup language) format.

In a possible implementation, the configuration file types supported by annotation information include:

(1)Service configuration file

In the specific implementation process, this type of configuration file cannot be directly parsed, but following the "xx=xx" paradigm, the mark-file of this type of configuration file can use the name of the parameter item as the primary key (key), and mark the parameter items one by one.

(2) Common format files

During the specific implementation process, such configuration files can usually be directly recognized by the program and converted into corresponding data structures. For example, for the mark-file of the yaml format configuration file, the form "featureGates.Accelerators" can be used as the primary key, one by one. Label parameter items.

Figure 2 is another schematic flowchart of a configuration file update method provided by an embodiment of the present application. As shown in Figure 2, the method 200 may include the following steps.

Step S210, update requirement information (current-file) preparation: needs to be carried out before file update and upgrade. The configuration file is upgraded from an old version to a new version. The configuration file corresponding to the old version (ie, the first configuration file origin-file) has been exist. The configuration file in the new version needs to have a "reference object", that is, current-file. There are several parameter items in current-file, and the values are recommended in the new version. The relevant ranges of parameter items of origin-file and current-file can be seen in Figure 3, including: obsolete parameters, overlapping parameters and new parameters.

In a possible implementation, the preparation of current-file includes the following principles:

(1) There is no need to write the discarded parameter items to current-file.

(2) Parameter items that may overlap with origin-file (such as the overlapping parameters shown in Figure 3) are generally set to the default value of the parameter item. For some special parameter items, they can be set to fixed values, such as critical paths. Parameter items of this type.

(3) Parameter items unique to later versions (such as the new parameters shown in Figure 3) are generally set to the default value of the parameter item. This kind of parameter item is generally a newly added parameter in a later version of the configuration file, representing a new function or change.

In one embodiment, current-file may be a common file format to facilitate parsing.

Step S220, mark-file preparation: Marking needs to be done before file update and upgrade. All possible parameter items should be marked. The parameter item marks of each configuration file are saved in a mark file. The annotation file can be in a common format (such as yaml, json, etc.), which can facilitate the next step of file parsing.

Step S230, file parsing: File parsing is a preparatory step before comparison in the following step S240. It is necessary to parse origin-file, current-file and mark-file into structures that can be recognized by the program.

In specific implementation, configuration file types include: common format files and service configuration files. Among them, common development languages will support the parsing of universal format files, and there is no need to design parsing logic by yourself. Service configuration files usually have comments (for example, behavioral comments starting with #), parameter classification titles (the titles may correspond to multiple configuration items), and configuration items (usually in the format of "xxx=xxx").

Figure 4 is a schematic flow chart of service configuration file parsing provided by an embodiment of the present application. As shown in Figure 4, the process includes steps S410-S440:

Step S410: The parsing process starts and determines whether the next line can be read. If so, proceed to step S420; otherwise, it ends;

Step S420, whether it is a comment line, if so, return to step S410, otherwise proceed to step S430;

Step S430, remove the parameter classification title and separate parameter items according to commas;

Step S440: Separate the parameter item name and parameter value according to "=" in sequence, and store them in the parsing result list.

After analyzing origin-file, current-file and mark-file respectively, step S240 can be entered.

Step S240, configuration item comparison: obtain the parameter items and their annotation items in mark-file in turn, and compare each parameter item in origin-file and current-file according to the annotation type and update strategy of each parameter item. The comparison process here is the update process.

Step S250: Generate a new configuration file (ie, the above-mentioned second configuration file): After the comparison of all annotated items is completed, the results are summarized and a new configuration file is generated. At this time, the configuration file update and upgrade is completed.

Through the embodiment of this application, before the configuration file is updated and upgraded, each parameter item in the configuration file is marked, and then the marked parameter items are traversed, the corresponding update and upgrade strategy is executed for each parameter item, and then a new parameter is generated based on the update and upgrade results. configuration file. The embodiment of this application indicates the update strategy of each parameter item in the upgrade process by annotating the configuration file parameter items. On this basis, customized upgrades of each parameter item can be realized, and data problems in related technologies can be overcome. It also improves the efficiency and accuracy of configuration file upgrades.

Figures 5 to 8 are example flow charts of service configuration file updates provided by embodiments of the present application. Figure 5 shows the parsing process of service configuration file updates, and Figure 6 shows the preparation phase process of service configuration file updates. Figure 7 shows the comparison phase process of service configuration file update, and Figure 8 shows the result splicing phase process of service configuration file update.

As shown in Figure 5, the input items are three files, origin-file, current-file and mark-file. These three files are parsed respectively, mark-file is parsed into an array structure mark Arr, and origin-file is parsed into Dictionary object originMap, parses current-file into currentMap.

As shown in Figure 6, in the preparation stage for updating the service configuration file, based on mark Arr and currentMap, delete the obsolete parameters in originMap.

As shown in Figure 7, it is the comparison stage of service configuration file update. Corresponding to the above-mentioned step S240, the comparison operation is performed according to the annotation type and update strategy (useOrigin, useCurrent, merge, originBaseMerge, currentBaseMerge) of the parameter items.

As shown in Figure 8, the result splicing stage of the service configuration file update corresponds to the above-mentioned step S250. The records in currentMap are cyclically read, and the result string is converted and written into destFile to form a new configuration file.

Table 6 is an example of configuration file parameter update, as shown in Table 6:

Table 6

The configuration file parameter update method provided by the embodiment of the present application is based on pre-setting the type of each parameter item and the strategy that needs to be executed for the update. The parameter item can be identified during the update process, and the update strategy can be executed on the parameter item, thereby realizing the parameter Expected updates of items, such as retaining the values of parameter items before the upgrade, merging parameter items, etc. The embodiment of this application indicates the update strategy of each parameter item in the upgrade process by annotating the configuration file parameter items, which can realize customized upgrade of each parameter, and can also overcome the problem of data loss or missing in related technologies. problems and improve the efficiency and accuracy of upgrades.

Based on a similar inventive concept, embodiments of the present application also provide a configuration file updating device.

Figure 9 is a schematic structural diagram of a configuration file update device provided by an embodiment of the present application. As shown in Figure 9, the configuration file update device 900 includes: a configuration parameter acquisition unit 910, an update unit 920 and a second configuration file generation unit 930 ,in:

The configuration parameter acquisition unit 910 is used to acquire all configuration parameters in the first configuration file;

Update unit 920, configured to update each configuration parameter according to pre-generated annotation information, where the annotation information is used to indicate the update strategy of each configuration parameter;

The second configuration file generating unit 930 is configured to generate a second configuration file according to the result of the update process.

The update unit 920 updates all the configuration parameters in the first configuration file obtained by the configuration parameter acquisition unit 910 according to the pre-generated annotation information, and then the second configuration file generation unit 930 generates a second configuration file according to the update processing result, Since all configuration parameters in the configuration file are annotated, the problem of data loss or deletion in related technologies can be overcome, thereby improving the accuracy of configuration file updates.

In a possible implementation, the configuration file updating device further includes: an annotation information generating unit, the annotation information generating unit is configured to generate annotation information according to the update requirement information and all the above configuration parameters, the above update requirement information indicates the second configuration file Configuration parameters and their update requirements.

In a possible implementation, the configuration file updating device further includes: a format conversion unit configured to convert the first configuration file, annotation information, and update requirement information into a program-recognizable format.

In the specific implementation process, the above update strategies include: discard, use the current value, use the updated value, the union of the current value and the updated value based on the current value as the priority, and the combination of the current value and the updated value based on the updated value as the priority. Union etc.

When the update policy of the first configuration parameter is discarded, the annotation information of the first configuration parameter generated according to the above update requirement information is discarded. After the update is completed, the first configuration parameter is not included in the second configuration file.

The configuration file updating device in the embodiment of the present application may be a device or a part in the terminal. components, integrated circuits, or chips. The device may be a mobile terminal or a non-mobile terminal, which is not specifically limited in the embodiments of this application.

The configuration file updating device 900 in the embodiment of the present application may be a device with an operating system. The operating system can be an Android operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of this application.

The configuration file updating device provided by the embodiment of the present application can implement each process implemented by the terminal in the above method embodiment, and achieve the same technical effect. To avoid duplication, the details will not be described here.

Optionally, as shown in Figure 10, this embodiment of the present application also provides an electronic device 1000, which includes a processor 1010 and a memory 1020. The memory 1020 stores programs or instructions that can be run on the processor 1010. For example, when the electronic device 1000 is a terminal, when the program or instruction is executed by the processor 1010, each process of the above configuration file update method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, they will not be repeated here.

Embodiments of the present application also provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the program or instructions are executed by a processor, each process of the above configuration file update method embodiment is implemented, and can achieve The same technical effects will not be repeated here to avoid repetition.

Wherein, the processor is the processor in the electronic device described in the above embodiment. The readable storage media includes computer-readable storage media, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical disks, etc.

An embodiment of the present application further provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the above embodiment of the configuration file update method. Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.

Further, embodiments of the present application also provide a computer program product, the computer program The program product includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, each of the above configuration file updating method embodiments is implemented. The process can achieve the same technical effect. To avoid repetition, it will not be described again here.

It should be noted that, in this document, the terms "comprising", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or apparatus. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article or apparatus that includes that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited. Functions are performed in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. To perform the functions, for example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology. The computer software product is stored in a storage medium (such as ROM/RAM, disk , optical disk), including several instructions to cause a terminal (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of this application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Inspired by this application, many forms can be made without departing from the purpose of this application and the scope protected by the claims, all of which fall within the protection of this application.

Claims

A configuration file update method, including:

Get all configuration parameters in the first configuration file;

Update each configuration parameter according to pre-generated annotation information, where the annotation information is used to indicate the update strategy of each configuration parameter;

A second configuration file is generated according to the result of the update process.
The configuration file updating method according to claim 1, wherein the annotation information is generated in the following manner:

Annotation information is generated based on the update requirement information and all configuration parameters, where the update requirement information indicates the configuration parameters in the second configuration file and their update requirements.
The configuration file updating method according to claim 2, wherein before updating each configuration parameter according to the pre-generated annotation information, the method further includes:

Convert the first configuration file, the annotation information, and the update requirement information into a program-recognizable format.
The configuration file updating method according to claim 2, wherein the update strategy includes: discarding, and when the first configuration parameter is discarded, generating annotation information according to the update requirement information and the all configuration parameters includes:

Generating the annotation information of the first configuration parameter according to the update requirement information is discarded, wherein the first configuration parameter is not included in the second configuration file.
The configuration file update method according to claim 1, wherein the update strategy further includes one of the following: using the current value, using the updated value, based on the current value as the union of the current value and the updated value of the priority, based on the updated value. The value is the union of the current value and the updated value of the priority.
A configuration file updating device, wherein the device includes:

A configuration parameter acquisition unit, used to acquire all configuration parameters in the first configuration file;

An update unit, configured to update each configuration parameter according to pre-generated annotation information, where the annotation information is used to indicate an update strategy for each configuration parameter;

A second configuration file generating unit is configured to generate a second configuration file according to the result of the update process.
The configuration file updating device according to claim 6, wherein the device includes: a label information generating unit,

The annotation information generating unit is configured to generate annotation information according to update requirement information and all configuration parameters, where the update requirement information indicates the configuration parameters in the second configuration file and their update requirements.
The configuration file updating device according to claim 7, wherein the device further includes:

A format conversion unit configured to convert the first configuration file, the annotation information, and the update requirement information into a program-recognizable format.
An electronic device, including a processor and a memory. The memory stores programs or instructions that can be run on the processor. When the program or instructions are executed by the processor, the implementation of any one of claims 1-5 is achieved. The steps of the described configuration file update method.
A readable storage medium on which a program or instructions are stored. When the program or instructions are executed by a processor, the steps of the configuration file updating method according to any one of claims 1 to 5 are implemented.