TWI738719B - Setting file verification method and device based on serialization format - Google Patents

Abstract

The present invention provides a configuration file verification method and device based on a serialized format. Wherein, the configuration file verification method includes: obtaining the data content of the source table entry of the source configuration file and the data content of the target table entry of the target configuration file in the configuration file; The data content of the target table item is matched; and the verification result of the configuration file is generated according to the matching result. The configuration file verification method of the embodiment of the present invention can check the content of multiple configuration files to determine whether the relationship between the variables in the multiple configuration files meets expectations, which enriches the internal calibration of the configuration files. The inspection plan of the inspection, at the same time, reduces the situation of submission errors when the user submits the configuration file.

Description

Setting file verification method and device based on serialization format

The present invention relates to the field of Internet technology, and in particular to a method and device for checking a configuration file based on a serialized format.

Serialization is the process of converting an object into a byte stream to save it in memory, a database, or a file. Its main purpose is to save the state of the object so that it can be recreated when needed. Common serialization formats include xml, json, yaml format, etc.

At present, when users submit configuration files, some serializable standard formats need to be checked for legality to avoid user submission errors. For example, for a configuration file in json format (JavaScript Object Notation, a featherweight data exchange format), the legality of the configuration file can be verified through the json template, which defines the correspondence between variable names and values , If the variables and values in the configuration file match the corresponding relationship, the configuration file is considered legal, otherwise the configuration file is considered illegal.

However, the current problem is that the json template can only be checked for configuration files in the json format, and the legality check cannot be performed for the configuration files that are not in the json format. In addition, the json template can only be checked in a single configuration file Whether the variable and the value of is in accordance with the predefined format, the content of the verification is not rich.

The present invention aims to solve one of the technical problems in the related art at least to a certain extent.

To this end, the first objective of the present invention is to propose a configuration file verification method based on a serialized format. The configuration file verification method can verify the content of multiple configuration files and determine whether the multiple configuration files are Whether the interrelationship between the variables meets expectations, enriches the verification plan for the internal verification of the profile, and reduces the situation of submission errors when the user submits the profile.

The second objective of the present invention is to provide a configuration file verification device based on a serialized format.

In order to achieve the above objective, the first aspect of the present invention proposes a configuration file verification method based on a serialization format, including: obtaining the data content of the source table entry of the source configuration file and the target table of the target configuration file in the configuration file The data content of the item; the data content of the source entry and the data content of the target entry are matched according to a preset matching rule; and the verification result of the configuration file is generated according to the matching result.

According to the configuration file verification method of the embodiment of the present invention, the data content of the source entry of the source profile and the data content of the target entry of the target profile in the profile are matched according to a preset matching rule, so that multiple Check the content between the configuration files to determine the difference between the variables in multiple configuration files Whether the relationship is in line with expectations, enriches the verification plan for the internal verification of the configuration file, and reduces the submission errors when the user submits the configuration file.

In order to achieve the above objective, the second aspect of the present invention provides a configuration file verification device based on a serialization format, including: an acquisition module for acquiring the data content and the source entry of the source configuration file in the configuration file The data content of the target entry of the target profile; a matching module for matching the data content of the source entry with the data content of the target entry according to a preset matching rule; and a generation module, using Based on the matching result, the verification result of the profile is generated. The configuration file verification device of the embodiment of the present invention matches the data content of the source entry of the source profile and the data content of the target entry of the target profile in the profile according to a preset matching rule, so that multiple The content of each configuration file is checked to determine whether the relationship between the variables in multiple configuration files is in line with expectations, which enriches the check plan for checking the internal configuration files, and reduces the occurrence of users when submitting configuration files. Submit the wrong status.

The additional aspects and advantages of the present invention will be partially given in the following description, and some will become obvious from the following description, or be understood through the practice of the present invention.

S101, S102, S103‧‧‧Method steps

S301, S302, S303, S304‧‧‧Method steps

S701, S702, S703, S704, S705‧‧‧Method steps

100‧‧‧Get Module

200‧‧‧Matching Module

300‧‧‧Generate Module

400‧‧‧First Judgment Module

500‧‧‧Second Judgment Module

The above and/or additional aspects and advantages of the present invention will become obvious and easy to understand from the following description of the embodiments in conjunction with the accompanying drawings, in which: Figure 1 is a serialized format-based configuration file of an embodiment of the present invention Flowchart of the verification method; Figure 2 is a schematic diagram of a configuration file matching rule according to an embodiment of the present invention; Figure 3 is a flowchart of a configuration file verification method based on a serialized format in a specific embodiment of the present invention; Figure 4 Fig. 5 is a schematic diagram of the format specification of a profile directory of an embodiment of the present invention; Fig. 6 is a schematic diagram of a configuration file restriction rule of an embodiment of the present invention; Fig. 7 Is a flowchart of a configuration file verification method based on a serialized format in another specific embodiment of the present invention; FIG. 8 is a schematic structural diagram of a configuration file verification device based on a serialized format in an embodiment of the present invention; FIG. 9 is the present invention A schematic structural diagram of a configuration file verification device based on a serialized format according to a specific embodiment of the invention; and FIG. 10 is a schematic structural diagram of a configuration file verification device based on a serialized format according to another specific embodiment of the present invention.

The embodiments of the present invention are described in detail below. Examples of the embodiments are shown in the accompanying drawings, in which the same or similar reference numerals indicate the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the drawings are exemplary and are intended to explain the present invention. It cannot be understood as a limitation to the present invention.

In addition, the terms "first" and "second" are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include one or more of these features. In the description of the present invention, "plurality" means two or more than two, unless otherwise specifically defined.

Any process or method description described in the flowchart or described in other ways herein can be understood as a module, segment, or code that includes one or more executable instructions for implementing specific logical functions or steps of the process. Part, and the scope of the preferred embodiment of the present invention includes additional implementations, which may not be in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order according to the functions in question, This should be understood by those skilled in the art to which the embodiments of the present invention belong.

Fig. 1 is a flowchart of a configuration file verification method based on a serialized format according to an embodiment of the present invention.

As shown in Figure 1, the configuration file verification method includes:

S101: Obtain data content of a source entry in the source profile and data content of a target entry in the target profile in the profile.

Specifically, after the user submits the configuration file, the data content in the source entry of the original file in the configuration file is read first, and then the data content in the target entry of the target file in the configuration file is read.

S102: Match the data content of the source entry and the data content of the target entry according to a preset matching rule.

Specifically, different matching rules are distinguished and sorted by different rule numbers. FIG. 2 shows a schematic diagram of a matching rule of a configuration file according to an embodiment of the present invention. As shown in FIG. 2, the source configuration file defines the file name of the matching source, which may include wildcards to represent a group of files. The source entry defines the name of the specific entry in the original file, and wildcards can be used to match a group of entries.

Matching rules define four commonly used rule relationships, including equality rules, containment rules, mutual exclusion rules, and unique rules. Among them, the equality rule means that the data content in the source entry is exactly the same as the data content in the target entry; the inclusion rule means that the data content in the source entry includes the data content in the target entry; the mutually exclusive rule means that the data content in the source entry The data content of and the data content in the target entry cannot have an intersection; the unique rule means that there can be no intersection between the data content in the source entry. When the data content is checked according to the unique rule, only the data in the source entry The data content is checked, and the data content in the target table item is not checked, so the target file and the target table item can be ignored.

The target profile defines the file name that matches the target, and can contain wildcard characters to indicate a set of files. The target entry defines the name of a specific entry in the target file, and wildcards can be used to match a group of entries.

Furthermore, the content of the serializable configuration file is converted into a set of collection data according to the matching rules. After reading the data content of the source entry of the original file in the configuration file and the data content of the target entry of the destination file, The calculation relationship defined in the matching rules is used to calculate whether the data content in the source entry and the data content in the target entry meet the requirements.

S103: Generate a check result of the configuration file according to the matching result.

Specifically, if the data content of the source entry and the data content of the target entry meet the preset matching rules, a verification result that is correct for the configuration file verification is generated.

If the data content of the source table entry and the data content of the target table entry do not meet the preset matching rules, the configuration file generates a check result of a check error, and a prompt message of the configuration file check error is generated to feedback to the user.

According to the configuration file verification method of the embodiment of the present invention, the data content of the source entry of the source profile and the data content of the target entry of the target profile in the profile are matched according to a preset matching rule, so that multiple The content of each configuration file is checked to determine whether the relationship between the variables in multiple configuration files is in line with expectations, which enriches the check plan for checking the internal configuration files, and reduces the occurrence of users when submitting configuration files. Submit the wrong status.

Fig. 3 is a flowchart of a configuration file verification method based on a serialized format according to a specific embodiment of the present invention.

As shown in Figure 3, the configuration file verification method includes:

S301: Determine whether the file directory of the profile meets the structure rule according to the preset structure rule.

Specifically, it is checked whether the format of the configuration file meets expectations, and the file directory format of the configuration file is checked.

In an embodiment of the present invention, the preset structure rules include type rules and content rules, to determine whether the type of the file directory meets the type rules, and if the type of the file directory does not meet the type rules, a prompt of configuration file verification error is generated Information, if the type of the file directory meets the type rules, further judgment Whether the content of the file directory meets the content rules, if the content of the file directory does not meet the content rules, a prompt message of configuration file verification errors will be generated. Specifically, FIG. 4 is a schematic diagram of the structure rule of an embodiment of the present invention. As shown in FIG. 4, the structure rule defines the file type and content rule of each file that needs to be checked. For a directory, the file type is defined as After the catalog, you need to define the contents of the catalog, and you can continue to define the sub-directories or files in the catalog under the contents of the catalog. For files, after defining the type as a file, define the content of the file and use it to check the content of the file in the next step. If the file directory of the configuration file does not conform to the structural rules, for example, the content of the file directory does not contain required files and the required directory does not exist, a configuration file verification error prompt information is generated to feedback to the user, or the type of the file directory does not match , And also generate prompt information about configuration file verification errors to give back to the user.

For example, FIG. 5 is a schematic diagram of the format specification of the file directory of the configuration file according to an embodiment of the present invention. As shown in FIG. 5, the top-level directory includes a cluster configuration file, a system configuration file, and a service list directory. Each service under the service list directory has its own service directory, configuration file directory, and service configuration directory. The configuration files used by the service are placed in the service directory. The configuration files include deployment configuration files and version configuration files. The configuration directory includes service upgrade configuration files, and the service configuration directory includes user configuration files. Furthermore, it is checked whether the file directory structure of the profile meets the requirements according to the above-mentioned format specification.

In an embodiment of the present invention, the preset structure rules also include constraint rules, which determine whether the content of the file directory meets the constraint rules. If the content of the file directory does not meet the constraint rules, a configuration file verification error is generated. Reminder information. Specifically, in addition to the file directory format of the configuration file In addition to checking, it also checks the constraints between the contents of the file directory of the configuration file. For example, Figure 6 is a schematic diagram of a profile constraint rule of an embodiment of the present invention. As shown in Figure 6, if a machine list is defined in the cluster profile, the deployment profile also contains the machine list, and the configuration file in the deployment profile The machine list should be included in the machine list in the cluster configuration file. Another example is the role list of the service defined in the deployment profile, the version profile also contains the role list, and the upgrade profile also contains the role list. Furthermore, according to the requirements of different applications, a variety of different constraint rules can be defined, and the content of the file directory of the profile can be checked according to these constraint rules.

S302: Acquire the data content of the source entry of the source profile and the data content of the target entry of the target profile in the profile.

Specifically, after the user submits the configuration file, the data content in the source entry of the original file in the configuration file is read first, and then the data content in the target entry of the target file in the configuration file is read.

S303: Match the data content of the source entry and the data content of the target entry according to a preset matching rule.

Specifically, different matching rules are distinguished and sorted by different rule numbers. FIG. 2 shows a schematic diagram of a matching rule of a configuration file according to an embodiment of the present invention. As shown in FIG. 2, the source configuration file defines the file name of the matching source, which may include wildcards to represent a group of files. The source entry defines the name of the specific entry in the original file, and wildcards can be used to match a group of entries.

Matching rules define four commonly used rule relationships, including equality rules, containment rules, mutual exclusion rules, and unique rules. Among them, the equality rule means that the data content in the source entry is completely the same as the data content in the target entry. Same; containment rules indicate that the data content in the source entry includes the data content in the target entry; mutually exclusive rules indicate that the data content in the source entry and the data content in the target entry cannot overlap; the only rule indicates that the source entry There can be no intersection between the data content in the data content. When the data content is checked according to the unique rule, only the data content in the source table item is checked, and the data content in the target table item is not checked, so the destination file can be ignored And the target table entry.

The target profile defines the file name that matches the target, and can contain wildcard characters to indicate a set of files. The target entry defines the name of a specific entry in the target file, and wildcards can be used to match a group of entries.

Furthermore, the content of the serializable configuration file is converted into a set of collection data according to the matching rules. After reading the data content of the source entry of the original file in the configuration file and the data content of the target entry of the destination file, The calculation relationship defined in the matching rules is used to calculate whether the data content in the source entry and the data content in the target entry meet the requirements.

S304: Generate a check result of the configuration file according to the matching result.

Specifically, if the data content of the source entry and the data content of the target entry meet the preset matching rules, a verification result that is correct for the configuration file verification is generated.

If the data content of the source table entry and the data content of the target table entry do not meet the preset matching rules, the configuration file generates a check result of a check error, and a prompt message of the configuration file check error is generated to feedback to the user.

The configuration file verification method of the embodiment of the present invention judges whether the file directory of the configuration file satisfies the structure rule according to the preset structure rule, so that multiple The file directory structure of each configuration file is checked to check whether the structure of the configuration file meets expectations, which further enriches the check plan for checking the inside of a single configuration file.

FIG. 7 is a flowchart of a configuration file verification method based on a serialized format according to another specific embodiment of the present invention.

As shown in Figure 7, the configuration file verification method includes:

S701: Determine whether the file directory of the profile meets the structure rule according to the preset structure rule.

Specifically, it is checked whether the format of the configuration file meets expectations, and the file directory format of the configuration file is checked.

In an embodiment of the present invention, the preset structure rules include type rules and content rules, to determine whether the type of the file directory meets the type rules, and if the type of the file directory does not meet the type rules, a prompt of configuration file verification error is generated Information, if the type of the file directory meets the type rule, it is further determined whether the content of the file directory meets the content rule, and if the content of the file directory does not meet the content rule, a prompt message of configuration file verification error is generated. Specifically, FIG. 4 is a schematic diagram of the structure rule of an embodiment of the present invention. As shown in FIG. 4, the structure rule defines the file type and content rule of each file that needs to be checked. For a directory, the file type is defined as After the catalog, you need to define the contents of the catalog, and you can continue to define the sub-directories or files in the catalog under the contents of the catalog. For files, after defining the type as a file, define the content of the file and use it to check the content of the file in the next step. If the file directory of the configuration file does not conform to the structural rules, for example, the content of the file directory does not contain the required files and the required directory does not exist, a prompt message of configuration file verification errors will be generated Feedback to the user, or the type of the file directory does not match, and a prompt message of configuration file verification error is also generated to feedback to the user.

For example, FIG. 5 is a schematic diagram of the format specification of the file directory of the configuration file according to an embodiment of the present invention. As shown in FIG. 5, the top-level directory includes a cluster configuration file, a system configuration file, and a service list directory. Each service under the service list directory has its own service directory, configuration file directory, and service configuration directory. The configuration files used by the service are placed in the service directory. The configuration files include deployment configuration files and version configuration files. The configuration directory includes service upgrade configuration files, and the service configuration directory includes user configuration files. Furthermore, it is checked whether the file directory structure of the profile meets the requirements according to the above-mentioned format specification.

In an embodiment of the present invention, the preset structure rules also include constraint rules, which determine whether the content of the file directory meets the constraint rules. If the content of the file directory does not meet the constraint rules, a configuration file verification error is generated. Reminder information. Specifically, in addition to checking the file directory format of the profile, it also checks the constraints between the contents of the file directory of the profile. For example, Figure 6 is a schematic diagram of the configuration file constraint rules of an embodiment of the present invention. The machine list should be included in the machine list in the cluster configuration file. Another example is the role list of the service defined in the deployment profile, the version profile also contains the role list, and the upgrade profile also contains the role list. Furthermore, according to the requirements of different applications, a variety of different constraint rules can be defined, and the content of the file directory of the profile can be checked according to these constraint rules.

S702: Determine whether the content of the configuration file is based on the preset serialized file template Whether it meets the specifications.

Specifically, the content of a single configuration file is checked. For example, a general json serialized file template is used to check the content of the configuration and files. The json file template can achieve a richer content check within a single file, and the inspection process can be Make it interactive or non-interactive. For example, the application uses the json template to check user input to ensure that the input content meets the application's specifications.

If the content of the configuration file does not conform to the specification, a prompt message of configuration file verification error will be generated.

S703: Acquire the data content of the source entry of the source profile and the data content of the target entry of the target profile in the profile.

Specifically, after the user submits the configuration file, the data content in the source entry of the original file in the configuration file is read first, and then the data content in the target entry of the target file in the configuration file is read.

S704: Match the data content of the source entry and the data content of the target entry according to a preset matching rule.

Specifically, different matching rules are distinguished and sorted by different rule numbers. FIG. 2 shows a schematic diagram of a matching rule of a configuration file according to an embodiment of the present invention. As shown in FIG. 2, the source configuration file defines the file name of the matching source, which may include wildcards to represent a group of files. The source entry defines the name of the specific entry in the original file, and wildcards can be used to match a group of entries.

Matching rules define four commonly used rule relationships, including equality rules, containment rules, mutual exclusion rules, and unique rules. Among them, the equality rule means that the data content in the source entry is completely the same as the data content in the target entry. Same; containment rules indicate that the data content in the source entry includes the data content in the target entry; mutually exclusive rules indicate that the data content in the source entry and the data content in the target entry cannot overlap; the only rule indicates that the source entry There can be no intersection between the data content in the data content. When the data content is checked according to the unique rule, only the data content in the source table item is checked, and the data content in the target table item is not checked, so the destination file can be ignored And the target table entry.

The target profile defines the file name that matches the target, and can contain wildcard characters to indicate a set of files. The target entry defines the name of a specific entry in the target file, and wildcards can be used to match a group of entries.

Furthermore, the content of the serializable configuration file is converted into a set of collection data according to the matching rules. After reading the data content of the source entry of the original file in the configuration file and the data content of the target entry of the destination file, The calculation relationship defined in the matching rules is used to calculate whether the data content in the source entry and the data content in the target entry meet the requirements.

S705: Generate a check result of the configuration file according to the matching result.

Specifically, if the data content of the source entry and the data content of the target entry meet the preset matching rules, a verification result that is correct for the configuration file verification is generated.

If the data content of the source table entry and the data content of the target table entry do not meet the preset matching rules, the configuration file generates a check result of a check error, and a prompt message of the configuration file check error is generated to feedback to the user.

In the configuration file verification method of the embodiment of the present invention, in order to ensure that the configuration file submitted by the user meets expectations, three verifications are performed on the configuration file. Check the file directory format of the file, check the content of a single configuration file, and check the content association between multiple configuration files. This not only enriches the check plan for checking the configuration file, but also Greatly improve the accuracy of the configuration file verification, and reduce the submission errors when the user submits the configuration file.

In order to implement the above embodiments, the present invention also provides a configuration file verification device based on a serialized format.

FIG. 8 is a schematic structural diagram of a configuration file verification device based on a serialized format according to an embodiment of the present invention.

As shown in FIG. 8, the configuration file verification device includes: an acquisition module 100, a matching module 200 and a generation module 300.

Specifically, the acquisition module 100 is used to acquire the data content of the source entry of the source profile and the data content of the target entry of the target profile in the profile.

The matching module 200 is configured to match the data content of the source entry with the data content of the target entry according to a preset matching rule. Among them, the preset matching rules include equality rules, containment rules, mutual exclusion rules, and unique rules.

The generating module 300 is used for generating the verification result of the profile according to the matching result. Wherein, the generating module 300 is also used to generate a prompt message of a configuration file verification error when the data content of the source entry and the data content of the target entry do not meet the preset matching rules.

It should be noted that the foregoing explanation of the embodiment of the configuration file verification method is also applicable to the configuration file verification device of this embodiment, and the implementation principle is similar, and will not be repeated here.

The configuration file verification device of the embodiment of the present invention matches the data content of the source entry of the source profile and the data content of the target entry of the target profile in the profile according to a preset matching rule, so that multiple The content of each configuration file is checked to determine whether the relationship between the variables in multiple configuration files is in line with expectations, which enriches the check plan for checking the internal configuration files, and reduces the occurrence of users when submitting configuration files. Submit the wrong status.

FIG. 9 is a schematic structural diagram of a configuration file verification device based on a serialized format according to a specific embodiment of the present invention.

As shown in FIG. 9, the configuration file verification device includes: an acquisition module 100, a matching module 200, a generation module 300, and a first judgment module 400.

Specifically, the first judging module 400 is used to judge whether the file directory of the profile meets the structure rule according to a preset structure rule.

Wherein, when the preset structure rules include type rules and content rules, the first judging module 400 is also used to judge whether the type of the file directory meets the type rules, and the generation module 300 is also used to determine whether the type of the file directory does not meet the type. When the rule is set, the prompt information of the configuration file verification error is generated. The first judgment module 400 is also used for further judging whether the content of the file directory meets the content rule when the type of the file directory meets the type rule, and the generation module 300 is also used for When the content of the file directory does not meet the content rules, a prompt message of configuration file verification error is generated.

Wherein, when the preset structural rules also include constraint rules, the first judgment module 400 is also used to judge whether the content of the file directory meets the constraint rules, and the generation module 300 is also used to determine whether the content of the file directory meets the constraint rules. Satisfy constraints When setting rules, a prompt message for configuration file verification errors is generated.

It should be noted that the foregoing explanation of the embodiment of the configuration file verification method is also applicable to the configuration file verification device of this embodiment, and the implementation principle is similar, and will not be repeated here.

The configuration file verification device of the embodiment of the present invention judges whether the file directory of the configuration file meets the structure rules according to the preset structure rules, so that the file directory structure of multiple configuration files can be verified to check whether the structure of the configuration files conforms to the structure rules. It is expected that the verification plan for the verification of a single profile will be further enriched.

FIG. 10 is a schematic structural diagram of a configuration file verification device based on a serialized format according to another specific embodiment of the present invention.

As shown in FIG. 10, the configuration file verification device includes: an acquisition module 100, a matching module 200, a generation module 300, a first judgment module 400, and a second judgment module 500.

Specifically, the second judgment module 500 is used for judging whether the content of the configuration file meets the specification according to a preset serialized file template.

The generating module 300 is also used to generate a prompt message of a configuration file verification error when the content of the configuration file does not conform to the specification.

It should be noted that the foregoing explanation of the embodiment of the configuration file verification method is also applicable to the configuration file verification device of this embodiment, and the implementation principle is similar, and will not be repeated here.

In the configuration file verification device of the embodiment of the present invention, in order to ensure that the configuration file submitted by the user meets expectations, three verifications are performed on the configuration file. Enter Perform a check, and finally check the content association between multiple configuration files, which not only enriches the check plan for checking the configuration file, but also greatly improves the accuracy of the configuration file check and reduces the number of users submitting settings. There was a submission error while filing.

It should be understood that each part of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in memory and executed by a suitable instruction execution system. For example, if it is implemented by hardware, as in another embodiment, it can be implemented by any one or a combination of the following technologies known in the art: having a logic gate circuit for implementing logic functions on data signals Discrete logic circuit, dedicated integrated circuit with suitable combinational logic gate circuit, programmable grid array (PGA), field programmable grid array (FPGA), etc.

In the description of this specification, descriptions with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" etc. mean specific features described in conjunction with the embodiment or example , Structures, materials or features are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the described specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine the different embodiments or examples and the features of the different embodiments or examples described in this specification without contradicting each other.

Although the embodiments of the present invention have been shown and described above, it can be understood It is understood that the above-mentioned embodiments are exemplary and should not be construed as limiting the present invention. Those of ordinary skill in the art can make changes, modifications, substitutions and modifications to the above-mentioned embodiments within the scope of the present invention.

Claims (14)

A configuration file verification method based on a serialized format, characterized in that the configuration file verification method includes the following steps: obtaining data content of the source entry of the source profile and data of the target entry of the target profile in the profile Content; match the data content of the source entry with the data content of the target entry according to a preset matching rule; and generate a verification result of the profile based on the matching result, where, if the preset matching result is satisfied , It is determined that the relationship between the variables in the multiple configuration files is in line with expectations, and the configuration file is determined to be legal, otherwise, it is determined that the relationship between the variables in the multiple configuration files does not meet expectations, and the configuration file is determined The format of is not legal. For example, in the configuration file verification method described in item 1 of the scope of patent application, the preset matching rules include an equality rule, an inclusion rule, a mutual exclusion rule, and a unique rule. For example, the configuration file verification method described in item 1 or 2 of the scope of patent application, wherein the verification result of the configuration file is generated according to the matching result, including: if the data content of the source entry and the data of the target entry If the content does not meet the preset matching rules, a prompt message for the verification error of the profile will be generated. For example, the configuration file verification method described in item 1 of the scope of patent application, wherein, before obtaining the data content of the source table entry of the source configuration file and the data content of the target table entry of the target configuration file in the configuration file, the method further includes: Determine whether the file directory of the profile meets the structure rule according to the preset structure rule. For example, the configuration file verification method described in item 4 of the scope of patent application, wherein the preset structure rule includes a type rule and a content rule, and it is determined whether the file directory of the profile meets the structure rule according to the preset structure rule , Including: judging whether the type of the file directory meets the type rule; if the type of the file directory does not meet the type rule, a prompt message of the configuration file verification error is generated; if the type of the file directory meets the type rule, It is further judged whether the content of the file directory meets the content rule; and if the content of the file directory does not meet the content rule, a prompt message of the configuration file verification error is generated. For example, the configuration file verification method described in item 5 of the scope of patent application, wherein the preset structure rule further includes a constraint rule, and the file directory of the configuration file is determined according to the preset structure rule whether the file directory of the configuration file satisfies the structure rule, including : Determine whether the content of the file directory meets the constraint rule; and if the content of the file directory does not meet the constraint rule, a prompt message of the configuration file verification error will be generated. For example, the configuration file verification method described in item 1 of the scope of patent application, wherein, before acquiring the data content of the source entry of the source profile and the data content of the target entry of the target profile in the profile, the method further includes: Determine whether the content of the profile matches the default serialized file template Compliance; and if the content of the profile does not meet the specifications, a prompt message will be generated that the profile is checked incorrectly. A configuration file verification device based on a serialized format, characterized in that the configuration file verification device includes: an acquisition module for acquiring the data content of the source entry of the source profile and the target of the target profile in the profile The data content of the entry; the matching module is used to match the data content of the source entry and the data content of the target entry according to the preset matching rules; and the generation module is used to generate the setting based on the matching result The check result of the file, where, if the preset matching result is satisfied, it is determined that the relationship between the variables in the multiple configuration files is in accordance with the expectation, and the format of the configuration file is determined to be legal, otherwise, multiple The relationship between the variables in the configuration file does not meet expectations, and it is determined that the format of the configuration file is not legal. As described in item 8 of the scope of patent application, the preset matching rule includes an equality rule, an inclusion rule, a mutual exclusion rule, and a unique rule. For example, the configuration file verification device described in item 8 or 9 of the scope of patent application, wherein the generation module is also used for: when the data content of the source entry and the data content of the target entry do not meet the preset When the rules are matched, a prompt message for the verification error of the profile is generated. Such as the configuration file verification device described in item 8 of the scope of patent application, Wherein, it further includes: a first judging module for judging whether the file directory of the profile meets the structure rule according to a preset structure rule. For example, the configuration file verification device described in item 11 of the scope of patent application, wherein the preset structure rule includes a type rule and a content rule, and the first judgment module is also used for judging whether the type of the file directory satisfies the Type rule; the generation module is also used to generate the prompt information of the configuration file verification error when the type of the file directory does not meet the type rule; the first judgment module is also used to indicate that the type of the file directory meets the In the case of this type of rule, it is further determined whether the content of the file directory meets the content rule; and the generation module is also used to generate the prompt information of the configuration file verification error when the content of the file directory does not meet the content rule. For example, the configuration file verification device described in item 12 of the scope of patent application, wherein the preset structural rules also include constraint rules, and the first judgment module is also used for judging whether the content of the file directory satisfies the Constraint rules; and the generation module is also used to generate the configuration file verification error prompt information when the content of the file directory does not meet the constraint rules. For example, the configuration file verification device described in item 8 of the scope of patent application further includes: a second judgment module for judging whether the content of the configuration file meets the specification according to the preset serialized file template; The generating module is also used to generate the prompt information of the configuration file verification error when the content of the configuration file does not meet the specifications.

Images