CN117667129A - Configuration file updating method and device, electronic equipment and readable storage medium - Google Patents

Abstract

The application discloses a method, a device, an electronic device and a readable storage medium for updating a configuration file, wherein the method comprises the following steps: acquiring all configuration parameters in a first configuration file; updating each configuration parameter according to pre-generated labeling information, wherein the labeling information is used for indicating an updating strategy of each configuration parameter; and generating a second configuration file according to the result of the updating process. By the method and the device, the problem of data loss or deletion in the related technology can be solved, so that the accuracy of updating the configuration file can be improved.

Description

Configuration file updating method and device, electronic equipment and readable storage medium

Technical Field

The application belongs to the technical field of data processing, and particularly relates to a method and device for updating a configuration file, electronic equipment and a readable storage medium.

Background

Currently, to better accommodate the technological evolution, the parameter updates between upgrades or versions of application configuration files are frequent. The main ways of updating the parameters of the current configuration file (which may be simply referred to as configuration parameters) are: only the parameters which need to be updated are updated, and other parameters which do not need to be updated are not considered, so that part of parameters are missing in the subsequent version, and maintenance of the subsequent version parameters is not facilitated.

That is, the related configuration parameter updating method has the problem of data loss or missing.

Disclosure of Invention

An object of the embodiments of the present application is to provide a method, an apparatus, an electronic device, and a readable storage medium for updating a configuration file, which can solve the problem of data loss or loss in a configuration parameter updating manner in the related art.

In a first aspect, an embodiment of the present application provides a method for updating a configuration file, including:

acquiring all configuration parameters in a first configuration file;

updating each configuration parameter according to pre-generated labeling information, wherein the labeling information is used for indicating an updating strategy of each configuration parameter;

and generating a second configuration file according to the updating processing result.

In a second aspect, an embodiment of the present application provides a configuration file updating apparatus, where the apparatus includes:

the configuration parameter acquisition unit is used for acquiring all configuration parameters in the first configuration file;

the updating unit is used for updating each configuration parameter according to pre-generated labeling information, wherein the labeling information is used for indicating an updating strategy of each configuration parameter;

and the second configuration file generating unit is used for generating a second configuration file according to the updating processing result.

In a third aspect, embodiments of the present application provide an electronic device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, the program or instruction implementing the steps of the method according to the first aspect when executed by the processor.

In a fourth aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which when executed by a processor implement the steps of the method according to the first aspect.

In the embodiment of the application, all the configuration parameters in the first configuration file are respectively updated according to the pre-generated labeling information, and the second configuration file is generated according to the updating result, and the problem of data loss or deletion in the related art can be solved due to labeling of all the configuration parameters in the configuration file, so that the updating accuracy of the configuration file can be improved.

Drawings

FIG. 1 is a schematic flow chart of a method for updating a configuration file according to an embodiment of the present application;

FIG. 2 is another flow chart of a method for updating a configuration file according to an embodiment of the present application;

FIG. 3 is a schematic view of a parameter correlation range between a configuration file and update requirement information provided in an embodiment of the present application;

FIG. 4 is a schematic flow chart of service profile parsing provided in an embodiment of the present application;

FIG. 5 is an exemplary diagram of a parsing flow for a service profile update in accordance with an embodiment of the present application;

FIG. 6 is a flowchart illustrating an example of a preparation phase for a service profile update in accordance with an embodiment of the present application;

FIG. 7 is an exemplary diagram of an alignment phase flow for service profile update in accordance with an embodiment of the present application;

FIG. 8 is a flowchart illustrating an exemplary result splicing phase of service profile update according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a configuration file updating apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type and not limited to the number of objects, e.g., the first object may be one or more.

In view of the problem that the related art configuration parameter updating mode has data loss or deletion, the embodiment of the application provides a configuration file updating scheme, and the scheme obtains an updated configuration file by labeling all configuration parameters in the configuration file to be updated and updating all configuration parameters according to the labeling process.

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

Fig. 1 is a schematic flow chart of a method for updating a configuration file according to an embodiment of the present application, and the method 100 may be performed by a terminal device. In other words, the method may be performed by software or hardware installed at the terminal device. As shown in fig. 1, the method may include the following steps S110-S130.

S110: all configuration parameters in the first configuration file are acquired. The first configuration file refers to a configuration file that needs to be updated.

S120: and updating each configuration parameter according to pre-generated labeling information, wherein the labeling information is used for indicating the updating strategy of each configuration parameter.

S130: and generating a second configuration file according to the updating processing result.

According to the configuration file updating method, all configuration parameters in the first configuration file are respectively updated according to the pre-generated marking information, and the second configuration file is generated according to the updating result, and the problem of data loss or deletion in the related art can be solved due to the fact that all configuration parameters in the configuration file are marked, and accordingly accuracy of configuration file updating can be improved.

In one possible implementation manner, the labeling information may be generated according to the update requirement information and all the configuration parameters in the first configuration file, where the update requirement information is used to indicate the configuration parameters and the update requirements in the second configuration file.

In one possible implementation, before the update processing of S120, the first configuration file, the labeling information, and the update requirement information may be converted into formats that are recognizable by the program, so as to facilitate the update processing.

In one possible implementation, the update policy in step S120 may be discard (i.e., need not appear in the second profile), use a current value (i.e., use a parameter value in the first profile), use an updated value (i.e., use an updated value), a union of a current value and an updated value based on the current value being a priority, a union of a current value and an updated value based on the updated value being a priority, etc.

The union of the current value and the updated value based on the priority of the current value refers to: for a parameter (which may also be referred to as a parameter item), for example, the parameter type is a dictionary type (or referred to as a dictionary value), the current value may be referred to as a current list, the updated value may be referred to as an updated list, and if the two lists are different in value, the final value is the union of the two lists, and for the case where keys are the same but the values (values) are different, the value in the current list is taken. Similarly, the union of the current value and the updated value based on the updated value being the priority refers to the final value being the union of the two lists, and the value in the updated list is taken for the case where the keys (keys) are the same but the values (values) are different.

In one embodiment, when the update requirement information of a configuration parameter is obsolete, when the configuration parameter is marked, the update policy of the configuration parameter needs to be marked as obsolete. During the updating process, the configuration parameters are deleted, i.e. not included in the updated second configuration file.

In one possible implementation manner, when each parameter (hereinafter may be referred to as a parameter item) in the configuration file is respectively labeled, labeling information may specifically include: the type of the parameter item, the update strategy, the attached parameters of the parameter item, etc. The parameter item types herein may include a normal type (i.e., a normal value in table 1), an array type (i.e., a list value in table 1), a dictionary type (i.e., a dictionary value in table 1), and the like.

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

type(s)	Type annotation
		Integer (common value)	int、int32、int64...
Decimal (common value)	float、float32、float64...
		Character string (common value)	string
Boolean value (common value)	bool
		List value	list
Dictionary values	map

TABLE 1

Based on the above parameter item types, labeling examples of the update policies are shown in tables 2 to 4 below, and in the following examples, the first configuration file is called an origin-file, and the update requirement information is called a current-file.

Table 2 is an example of the update policy (i.e., policy name in table 2) labels for the normal values, as shown in table 2:

table 2 table 3 is an example of update policy labeling of list values, as shown in table 3:

table 3 table 4 is an example of update policy labeling of dictionary values, as shown in table 4:

TABLE 4 Table 4

In one possible implementation, if a parameter item does not want to exist after an update upgrade, it may be marked as obsolete, e.g., as deemphasized.

In one possible implementation, if the parameter item type is a list value or a dictionary value, some of the parameter items may have some small items, which may be noted in a decresting item (a code name) if it is not desired that some small items also exist after the update upgrade. If some small items of the parameter items are desired to exist anyway after the update upgrade, they can be noted in a comfirmItem (a code name). If some of the small items in the parameter are mutually exclusive, it is desirable to keep one of the values after the update, it can be noted in mutex item (a code name).

Table 5 is an example of the notations, as shown in Table 5:

TABLE 5

In one possible implementation, the annotation information (which may be referred to as mark-file) may be in a common file format, which facilitates program identification and parsing. For parameter labeling, it is required that all parameters to be labeled are within a known range, and all possible parameter items can be obtained by updating the path of the upgrade (low version- & gt high version).

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

In one possible implementation, the profile types supported by the annotation information include:

(1) Service profile

In a specific implementation process, such a configuration file cannot be directly parsed, but the mark-file of such a configuration file can use the name of the parameter item as a key to label the parameter items one by one, following the paradigm of "xx=xx".

(2) Universal format file

In a specific implementation, such configuration files may be generally directly identified by a program and converted into a corresponding data structure, for example, mark-files of a yaml format configuration file may be labeled with parameter items one by one using the form "featuregates.

Fig. 2 is another flow chart of a method for updating a configuration file according to an embodiment of the present application, and as shown in fig. 2, the method 200 may include the following steps.

Step S210, update requirement information (current-file) preparation: it is necessary to perform the update and upgrade of the configuration file from the old version to the new version, and the configuration file (i.e., the first configuration file origin-file) corresponding to the old version already exists. The configuration file in the new version needs to have a "reference", i.e. current-file. There are several parameter items in current-file, and the value is recommended in the new version. The relevant ranges of the parameters of the origin-file and the current-file can be seen in FIG. 3, and include: discard parameters, coincidence parameters, and new parameters.

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

(1) The discard parameter entries do not have to be written to current-file.

(2) The parameter item that may coincide with the registration-file (e.g., the coincidence parameter shown in fig. 3) is generally set to a default value for the parameter item, and for some special parameter items, may be set to a fixed value, such as a parameter item of the critical path type.

(3) The parameter item specific to the higher version (e.g., the new parameter shown in fig. 3) is typically set to a default value for the parameter item. Such parameter items are typically newly added parameters in a high-version configuration file, representing new functions or changes.

In one embodiment, the current-file may be in a universal file format, facilitating parsing.

Step S220, preparing a mark-file: the labeling is required to be carried out before updating and upgrading the file, all the possible parameter items are labeled, and the parameter item label of each configuration file is stored in one label file. The markup file may be in a general format (e.g., yaml, json, etc.) to facilitate further file parsing.

Step S230, file analysis: the file analysis is a preparation step before the comparison in step S240, and the origin-file, current-file and mark-file need to be respectively analyzed into structures identifiable by the program.

In particular implementations, the profile types include: a universal format file and a service configuration file. The general development language of the universal format file can support the analysis of the universal format file, and analysis logic does not need to be designed by the user. The service profile will typically have notes (e.g. # beginning behavior notes), parameter class headers (headers may correspond to multiple configuration items), and configuration items (typically in the format of "xxx=xxx").

Fig. 4 is a schematic flow chart of service profile parsing provided in the embodiment of the present application, as shown in fig. 4, the flow includes steps S410 to S440:

step S410, the analysis flow starts, whether the next row can be read is judged, if yes, step S420 is carried out, and if not, the process is ended;

step S420, if the line is the annotation line, returning to step S410 if the line is the annotation line, otherwise, proceeding to step S430;

step S430, removing parameter classification titles, and separating parameter items according to commas;

step S440, the parameter item names and the parameter values are sequentially separated according to "=" and stored in the analysis result list.

After the origin-file, current-file and mark-file are respectively parsed, step S240 can be entered.

Step S240, configuration item comparison: and sequentially acquiring parameter items and annotation items thereof in mark-file, and comparing each parameter item in the original-file and current-file according to the annotation type and the updating strategy of each parameter item, wherein the comparison process is an updating process.

Step S250, generating a new configuration file (i.e., the second configuration file described above): and after all the labeling items execute comparison, summarizing the results to generate a new configuration file, and updating and upgrading the configuration file.

Before updating and upgrading the configuration file, marking each parameter item in the configuration file, traversing the marked parameter items, executing a corresponding updating and upgrading strategy on each parameter item, and generating a new configuration file according to an updating and upgrading result. According to the embodiment of the application, the updating strategy of each parameter item in the updating process is shown through the labeling of the parameter items of the configuration file, on the basis, the customized updating of each parameter item can be realized, the problem of data loss or deletion in the related technology can be solved, and meanwhile, the efficiency and the accuracy of updating the configuration file are improved.

Fig. 5 to fig. 8 are exemplary flowcharts of service profile update provided in the embodiments of the present application, where fig. 5 shows a parsing flow of service profile update, fig. 6 shows a preparation phase flow of service profile update, fig. 7 shows a comparison phase flow of service profile update, and fig. 8 shows a result splicing phase flow of service profile update.

Referring to FIG. 5, the entries are three files, origin-file, current-file and mark-file, which are parsed respectively, the mark-file is parsed into a array structure mark Arr, origin-file is parsed into dictionary object originMap, and current-file is parsed into currentMap.

Referring to fig. 6, in the preparation phase for service profile update, discard parameters in the originMap are deleted based on mark Arr and currentMap.

Referring to fig. 7, in the comparison stage of updating the service configuration file, corresponding to the step S240, a comparison operation is performed according to the labeling type of the parameter item and the update policy (useOrigin, useCurrent, merge, originBaseMerge, currentBaseMerge).

Referring to fig. 8, in the result splicing stage of service profile update, corresponding to step S250, the record in currentMap is circularly read, and the result string is converted and written into destFile to form a new profile.

Table 6 is an example of profile parameter updates, as shown in table 6:

TABLE 6

According to the configuration file parameter updating method, based on the type of each parameter item and the strategy to be executed for updating, the parameter item can be identified in the updating process, the updating strategy is executed for the parameter item, and the expected updating of the parameter item is achieved, for example, the value of the parameter item before updating is reserved, the parameter item is combined, and the like. According to the embodiment of the application, the configuration file parameter items are marked, so that the updating strategy of each parameter item in the updating process is shown, the customized updating of each parameter can be realized, the problem of data loss or deletion in the related technology can be solved, and the updating efficiency and accuracy are improved.

Based on similar inventive concepts, the embodiment of the application also provides a configuration file updating device.

Fig. 9 is a schematic structural diagram of a configuration file updating apparatus according to an embodiment of the present application, as shown in fig. 9, the configuration file updating apparatus 900 includes: a configuration parameter acquisition unit 910, an update unit 920, and a second configuration file generation unit 930, wherein:

a configuration parameter obtaining unit 910, configured to obtain all configuration parameters in the first configuration file;

an updating unit 920, configured to update each configuration parameter according to pre-generated labeling information, where the labeling information is used to indicate an update policy of each configuration parameter;

and a second profile generating unit 930, configured to generate a second profile according to the result of the update process.

The updating unit 920 performs the updating process on all the configuration parameters in the first configuration file acquired by the configuration parameter acquiring unit 910 according to the pre-generated labeling information, and then the second configuration file generating unit 930 generates the second configuration file according to the updating process result, and the problem of data loss or deletion in the related art can be overcome due to labeling all the configuration parameters in the configuration file, so that the updating accuracy of the configuration file can be improved.

In one possible implementation, the configuration file updating apparatus further includes: and the annotation information generation unit is used for generating annotation information according to the update requirement information and all the configuration parameters, wherein the update requirement information indicates the configuration parameters and the update requirements of the configuration parameters in the second configuration file.

In one possible implementation, the configuration file updating apparatus further includes: and the format conversion unit is used for converting the first configuration file, the labeling information and the update requirement information into formats which can be identified by the program.

In a specific implementation process, the update policy includes: discarding, using a current value, using an updated value, a union of a current value and an updated value based on the current value as a priority, a union of a current value and an updated value based on the updated value as a priority, etc.

When the update strategy of the first configuration parameter is abandoned, generating marking information of the first configuration parameter according to the update requirement information as abandoned, wherein the first configuration parameter is not contained in the second configuration file after the update is completed.

The configuration file updating device in the embodiment of the application may be a device, or may be a component, an integrated circuit, or a chip in a terminal. The device may be a mobile terminal or a non-mobile terminal, and embodiments of the present application are not specifically limited.

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

The configuration file updating apparatus provided in the embodiment of the present application can implement each process implemented by the terminal in the embodiment of the method, and achieve the same technical effect, so that repetition is avoided, and no redundant description is provided herein.

Optionally, as shown in fig. 10, the embodiment of the present application further provides an electronic device 1000, including a processor 1010 and a memory 1020, where a program or an instruction that can be executed on the processor 1010 is stored in the memory 1020, for example, when the electronic device 1000 is a terminal, the program or the instruction is executed by the processor 1010 to implement each process of the above-mentioned configuration file updating method embodiment, and the same technical effects can be achieved. In order to avoid repetition, a description thereof is omitted.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction realizes each process of the embodiment of the configuration file updating method, and the same technical effects can be achieved, so that repetition is avoided, and no further description is provided herein.

Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium such as a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.

The embodiment of the application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled with the processor, and the processor is configured to run a program or an instruction, implement each process of the above embodiment of the method for updating a configuration file, and achieve the same technical effect, so that repetition is avoided, and no further description is provided here.

Further, the embodiment of the present application further provides a computer program product, where the computer program product includes a processor, a memory, and a program or an instruction stored in the memory and capable of running on the processor, where the program or the instruction when executed by the processor implements each process of the embodiment of the method for updating a configuration file, and the process can achieve the same technical effect, and for avoiding repetition, a description is omitted herein.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims (10)

1. A method for updating a configuration file, comprising:

acquiring all configuration parameters in a first configuration file;

updating each configuration parameter according to pre-generated labeling information, wherein the labeling information is used for indicating an updating strategy of each configuration parameter;

and generating a second configuration file according to the updating processing result.

2. The profile updating method according to claim 1, wherein the annotation information is generated by:

and generating labeling information according to the update demand information and all the configuration parameters, wherein the update demand information indicates the configuration parameters and the update demands thereof in the second configuration file.

3. The profile updating method according to claim 2, wherein before updating each configuration parameter based on the pre-generated labeling information, the method further comprises:

and converting the first configuration file, the labeling information and the update requirement information into formats which can be identified by programs.

4. The profile updating method according to claim 2, wherein the updating policy includes: discarding, when the first configuration parameter is discarding, generating the labeling information according to the update requirement information and the all configuration parameters includes:

generating labeling information of the first configuration parameters according to the updating demand information, wherein the first configuration parameters are not contained in the second configuration file.

5. The profile updating method of claim 1, wherein the updating policy further comprises one of: the method includes using a current value, using an updated value, a union of the current value and the updated value that are prioritized based on the current value, and a union of the current value and the updated value that are prioritized based on the updated value.

6. A profile updating apparatus, the apparatus comprising:

the configuration parameter acquisition unit is used for acquiring all configuration parameters in the first configuration file;

the updating unit is used for updating each configuration parameter according to pre-generated labeling information, wherein the labeling information is used for indicating an updating strategy of each configuration parameter;

and the second configuration file generating unit is used for generating a second configuration file according to the updating processing result.

7. The profile updating apparatus according to claim 6, wherein the apparatus comprises: the label information generating unit is used for generating label information,

the annotation information generating unit is used for generating annotation information according to the update requirement information and all the configuration parameters, wherein the update requirement information indicates the configuration parameters and the update requirements of the configuration parameters in the second configuration file.

8. The profile updating apparatus according to claim 7, wherein the apparatus further comprises:

and the format conversion unit is used for converting the first configuration file, the annotation information and the update requirement information into formats which can be identified by the program.

9. An electronic device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the profile updating method of any one of claims 1-5.

10. A readable storage medium, characterized in that the readable storage medium has stored thereon a program or instructions which, when executed by a processor, implement the steps of the profile updating method according to any one of claims 1-5.