Configuration updating method and device, control terminal and storage medium

Abstract

The embodiment of the invention discloses a configuration updating method and device, a control terminal and a storage medium, and can solve the problem that at present, configuration updating is mainly performed by packaging an executable file and releasing the executable file through a gray release process, and a program needs to be restarted for configuration. Obtaining configuration updating content; according to the configuration updating content, gray version configuration information in the cloud platform is updated, and gray version configuration information locally cached in the target application program is updated; when it is detected that updating of the gray version configuration information is completed, the gray version configuration information is loaded through the target application program, running testing is conducted on the loaded target application program through the target test case, and a test result is obtained; and when the test result indicates that the gray version configuration information is not abnormal, synchronizing the gray version configuration information to the online version configuration information of the target application program to update the online version configuration information of the target application program stored in the cloud platform.

Description

Technical Field

[0001] This application relates to the field of configuration update technology, and in particular to a configuration update method, apparatus, control terminal and storage medium. Background Technology

[0002] Besides relying on binary executable files, program execution often depends on configuration files, especially in scenarios like recommendation systems, where numerous execution strategies are injected into the program flow through configuration. Modifications to these configurations directly impact online services and significantly affect their stability. Currently, configuration updates are primarily packaged with the executable file and released via a canary release process. This requires restarting the program after each update, which is time-consuming and reduces the efficiency of configuration updates. Summary of the Invention

[0003] Therefore, it is necessary to provide a configuration update method, apparatus, control terminal, and storage medium to address the aforementioned technical problems.

[0004] In a first aspect, embodiments of this application provide a configuration update method applied to a control terminal, the configuration update method comprising: Obtain configuration update content, which indicates the content that needs to be modified in the configuration file for the target application; Based on the configuration update content, update the grayscale version configuration information in the cloud platform, and update the grayscale version configuration information cached locally in the target application; When the grayscale version configuration information update is detected, the grayscale version configuration information is loaded through the target application, and the loaded target application is run and tested through the target test case to obtain the test results. The target test case is configured with the grayscale version configuration information. When the test results indicate that there are no abnormalities in the grayscale version configuration information, the grayscale version configuration information is synchronized to the online version configuration information of the target application to update the online version configuration information of the target application stored in the cloud platform.

[0005] Secondly, embodiments of this application provide a configuration update device configured in a control terminal, the configuration update device comprising: The acquisition module is used to acquire configuration update content, which indicates the content that needs to be modified in the configuration file of the target application; The processing module is used to update the grayscale version configuration information in the cloud platform according to the configuration update content, and update the grayscale version configuration information cached locally in the target application; The processing module is further configured to, when detecting that the grayscale version configuration information has been updated, load the grayscale version configuration information through the target application, and run the loaded target application through the target test case to obtain the test result, wherein the target test case is configured with the grayscale version configuration information; The processing module is further configured to synchronize the grayscale version configuration information to the online version configuration information of the target application when the test result indicates that there is no abnormality in the grayscale version configuration information, so as to update the online version configuration information of the target application stored in the cloud platform.

[0006] Thirdly, embodiments of this application provide a control terminal, the control terminal comprising: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the configuration update method in the first aspect of the embodiments of this application.

[0007] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a computer to execute the configuration update method of the first aspect of embodiments of this application. The computer-readable storage medium includes ROM / RAM, a magnetic disk, or an optical disk, etc.

[0008] Fifthly, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to perform some or all of the steps of any of the methods of the first aspect.

[0009] Sixthly, embodiments of this application provide an application publishing platform for publishing computer program products, wherein when the computer program product is run on a computer, the computer performs some or all of the steps of any of the methods of the first aspect.

[0010] Compared with the prior art, the embodiments of this application have the following beneficial effects: This application provides a configuration update method, apparatus, control terminal, and storage medium. The method involves obtaining configuration update content, which indicates the modifications needed for the configuration file of a target application. Based on the configuration update content, the method updates the grayscale version configuration information in the cloud platform and the grayscale version configuration information cached locally in the target application. When the grayscale version configuration information update is detected, the grayscale version configuration information is loaded into the target application, and the loaded target application is run and tested using target test cases. The test results are obtained, and the target test cases are configured with grayscale version configuration information. When the test results indicate that there are no anomalies in the grayscale version configuration information, the grayscale version configuration information is synchronized to the online version configuration information of the target application to update the online version configuration information of the target application stored in the cloud platform. In this approach, the target application's configuration files are stored in both gray-scale and online versions. The gray-scale configuration information in the local cache is updated first, and only after running tests to confirm that the gray-scale configuration information is normal is the online version's configuration information updated. Since only the modified content in the configuration information is updated, and it doesn't need to be packaged and released with the executable file, configuration updates do not require restarting the program, reducing the overhead of algorithm configuration modification and improving configuration update efficiency. Furthermore, updating the configuration information locally first and then running test cases ensures that the subsequent online version's configuration update process will not encounter failures, thus meeting the security requirements of configuration release. Attached Figure Description

[0011] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

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

[0013] Figure 1 This is a flowchart illustrating a configuration update method provided in an embodiment of this application. Figure 1 ; Figure 2 This is a flowchart illustrating a configuration update method provided in an embodiment of this application. Figure 2 ; Figure 3 This is an architecture diagram of a configuration update system provided in an embodiment of this application; Figure 4This is a schematic diagram of the structure of a configuration update device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a control terminal provided in an embodiment of this application. Detailed Implementation

[0014] To better understand the above-mentioned objectives, features, and advantages of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features of this application can be combined with each other. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0015] The terms "first" and "second," etc., used in the specification and claims of this application are used to distinguish different objects, rather than to describe a specific order of objects.

[0016] The terms “comprising” and “having”, and any variations thereof, in this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or device.

[0017] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0018] Besides relying on binary executable files, program execution often depends on configuration files, especially in scenarios like recommendations, where numerous execution strategies are injected into the program flow through configuration. Modifications to these configurations directly impact online services and significantly affect their stability; therefore, configuration releases should follow a canary release process. Canary release is a strategy for gradually rolling out new features or versions in software delivery, aiming to reduce risk and ensure user experience. It identifies potential problems early through small-scale testing, avoiding systemic failures caused by full releases. In the current system, configurations based on canary release schemes are only released bundled with the executable file, requiring program restarts, which is time-consuming and unsuitable for frequent configuration releases.

[0019] To address the aforementioned technical problems, embodiments of this application provide a configuration update method, apparatus, control terminal, and storage medium, such as... Figure 1 As shown, Figure 1 A flowchart of a configuration update method provided in this application embodiment, the method may include the following steps: 101. Obtain configuration update information.

[0020] In this application embodiment, the configuration update content can be used to indicate the content that needs to be modified for the configuration file of the target application. The configuration update content can be entered by the user, determined according to project requirements, or sent by other devices. This application does not make any specific limitations.

[0021] 102. Based on the configuration update content, update the grayscale version configuration information in the cloud platform and update the grayscale version configuration information cached locally in the target application.

[0022] It's important to note that two different versions of the configuration file can be stored: a gray-scale version configuration information and an online version configuration information. These correspond to gradual release and full release, respectively. The gray-scale version configuration information and the online version configuration information contain identical content, differing only in version and their roles in configuration updates. The online version configuration information can be understood as pushing the new version or feature directly to all users or service nodes without traffic splitting or user grouping. The gray-scale version configuration information can be understood as pushing the new version or feature only to a subset of users or service nodes, gradually verifying it through traffic splitting or user grouping, and continuously monitoring metrics. If an anomaly occurs, a rollback mechanism will be invoked to cancel the release. Both gray-scale and online version configuration information can be stored separately in the cloud platform and local cache. However, compared to the online version configuration information, the main function of the gray-scale version configuration information lies in modifications made in the local cache. In other words, the gray-scale version configuration information can be configured locally without affecting program operation, while the online version configuration information is mainly used for configuration modifications in the cloud platform. Updates to the online version configuration information can be directly synchronized to the program.

[0023] In this embodiment, the control terminal pre-stores grayscale version configuration information and online version configuration information, and the content of the grayscale version configuration information and the online version configuration information is the same. The grayscale version configuration information can be updated first, and the specific updated content is the configuration update content. That is, the grayscale version configuration information is updated according to the modifications to the configuration file content indicated by the configuration update content, and the updated grayscale version configuration information is obtained.

[0024] In some embodiments, since both the grayscale version configuration information and the online version configuration information can be stored in the cloud platform and the local cache respectively, when updating the grayscale version configuration information, the grayscale version configuration information in the cloud platform can be updated, and the grayscale version configuration information cached locally in the target application can be updated synchronously.

[0025] In some embodiments, during the process of updating the grayscale version configuration information, the progress of the grayscale version configuration information update can be monitored in real time, and the progress of the grayscale version configuration information update can be recorded as the first update progress. The initial progress of the first update progress is zero, and the final progress to be reached is 100%, indicating that the grayscale version configuration information update is complete.

[0026] 103. When the grayscale version configuration information update is detected, load the grayscale version configuration information through the target application, and run the target application after loading through the target test cases to obtain the test results.

[0027] In this embodiment, to ensure the normal updating and application of subsequent online version configuration information, it is necessary to detect the grayscale version configuration information. That is, the subsequent processing of the online version configuration information can be performed based on the detection results of the grayscale version configuration information. Therefore, when the grayscale version configuration information is updated, the grayscale version configuration information can be loaded through the target application, that is, the target application can be run according to the grayscale version configuration information, and the loaded target application can be run for testing. During testing, a target test case can be executed, which is configured with the grayscale version configuration information. In other words, to test whether there are any anomalies in the grayscale version configuration information, a target test case can be generated based on the grayscale version configuration information, and then the target application that has loaded the grayscale version configuration information can be run for testing using this target test case. The target test case can construct a test scenario based on the grayscale version configuration information and the target application to perform the test, thereby obtaining the test results. The test results can reflect whether there are any anomalies in the grayscale version configuration information.

[0028] 104. When the test results indicate that there are no abnormalities in the grayscale version configuration information, the grayscale version configuration information is synchronized to the online version configuration information of the target application to update the online version configuration information of the target application stored in the cloud platform.

[0029] In this embodiment of the application, after running the test, if the test result indicates that there is no abnormality in the gray-scale version configuration information, it means that both the gray-scale version configuration information and the online version configuration information can be configured normally for the application. Therefore, the gray-scale version configuration information can be synchronized to the online version configuration information of the target application. That is, based on the gray-scale version configuration information, the online version configuration information of the target application stored in the cloud platform is updated synchronously. At this time, the entire update process of the gray-scale version and the online version of the target application's configuration file can be completed.

[0030] This application provides a configuration update method that stores the configuration file of the target application in both grayscale and online versions. The grayscale version configuration information in the local cache is updated first, and only after running tests confirm that the grayscale version configuration information is normal is the online version configuration information updated. Since only the modified content in the configuration information is updated, and it does not need to be packaged and released with the executable file, configuration updates do not require restarting the program, reducing the overhead of algorithm configuration modification and improving configuration update efficiency. Furthermore, updating the configuration information locally first and then running test cases ensures that the update process of the subsequently updated online version configuration information will not encounter failures, thus satisfying the security of configuration release.

[0031] like Figure 2 As shown, Figure 2 A flowchart of a configuration update method provided in this application embodiment, the method may further include the following steps: 201. Obtain configuration update information.

[0032] In this embodiment, the description of step 201 is the same as the detailed description of step 101 in the above embodiments, and will not be repeated in this embodiment.

[0033] 202. Check if there are any tasks in the task release list that are in the release state.

[0034] In this embodiment, when new configuration information needs to be updated, the configuration update content needs to be published. However, a business can only publish one task at a time and cannot distribute them in parallel, which can easily cause data chaos. Therefore, after obtaining the configuration update content, before publishing it, the status of the tasks in the task publication list can be checked. The task status can include: unpublished, published, published, and published paused, which are used to represent the various stages of task publication. The published status indicates that the task is currently being published, while the unpublished, published, and published paused statuses all indicate that the task is not currently being published. If there is a task in the published status at this time, the configuration information of the node cannot be updated. Therefore, it is necessary to check whether there is a task in the published status in the task publication list.

[0035] 203. When a task in the publishing state is detected to be non-existent, add a process lock to the configuration update content.

[0036] In this embodiment of the application, after detecting the task status of each task in the task release list, if no task in the release status is detected, it means that no task is currently being released, and then the release process for the configuration update content can be started.

[0037] It should be noted that, in order to prevent parallel deployments, it is necessary to confirm that there are no other tasks being deployed before deploying configuration updates. Similarly, no other tasks can be deployed while the configuration updates are being deployed. Therefore, a process lock can be added to the configuration updates, which is equivalent to locking the task deployment process, preventing other tasks from being deployed and thus preventing parallel deployments.

[0038] 204. Based on the configuration update content, update the grayscale version configuration information in the cloud platform and update the grayscale version configuration information cached locally in the target application.

[0039] In this embodiment, the description of step 204 is the same as the detailed description of step 102 in the above embodiments, and will not be repeated in this embodiment.

[0040] 205. When the grayscale version configuration information update is detected, the traffic data of the target application is grayscale marked.

[0041] 206. Load the grayscale version configuration information through the target application.

[0042] 207. Collect grayscale traffic data of the target application, and test the target application based on the grayscale traffic data using the target test cases to obtain the test results.

[0043] In this embodiment of the application, during the process of grayscale marking of traffic data of the target application, the traffic data is the traffic required for the application to run. Specifically, the traffic data can be sent through the upstream route. The grayscale traffic data obtained after grayscale marking is used to run the grayscale version configuration information for testing. The running test here can be understood as detecting relevant indicators of traffic data during the running process to obtain test results. The test results can be used to indicate whether there are any abnormalities in the grayscale version configuration information.

[0044] In some embodiments, grayscale marking of traffic data can actually be a coloring operation, that is, coloring some traffic. Colored traffic can be called grayscale traffic, or marked traffic. The purpose of coloring is to divide traffic and distinguish the nodes through which different traffic flows, so that the nodes can perform different business operations. Specifically, traffic can be matched based on conditions such as user ID, region, device type, destination address, source address, and port number, and then a specific mark is attached to the matched traffic, such as: Differentiated Services CodePoint (DSCP) value, Virtual Local Area Network (VLAN) label, Multiprotocol Label Switching Experimental Use Field (MPLS EXP) bit, etc.

[0045] In some embodiments, traffic marking can be understood as traffic splitting, dividing traffic into normal traffic and gray-scale traffic. Different traffic flows to different nodes. For these gray-scale traffic, the marking of traffic is not done all at once, but the marking ratio is gradually increased. Initially, the marking progress is zero, and all traffic is normal. After the marking of traffic begins, some normal traffic will become gray-scale traffic. Gray-scale traffic is the traffic that is marked. The proportion of gray-scale traffic will gradually increase, and the proportion of gray-scale traffic is the traffic marking ratio. That is to say, the traffic marking ratio can be continuously recorded during the marking process. Initially, the traffic marking ratio is zero. Since the marked traffic data needs to be tested with the gray-scale version configuration information, in order to ensure that all traffic flowing through the gray-scale version is tested, the proportion of gray-scale traffic needs to be gradually increased to 100%, that is, all traffic is gray-scale traffic, which means that the marking is complete. During the marking process, the gray-scale configuration information can be continuously tested using the marked gray-scale traffic to obtain test results.

[0046] In some embodiments, the target application is tested based on grayscale traffic data using target test cases to obtain test results. Specifically, this may include: during the operation of the target application, obtaining test metrics of grayscale traffic data in real time through target test cases, the test metrics being used to describe the running status of the target application; when the test metrics are detected to be within a preset value range, it is determined that the test results indicate that there are no abnormalities in the grayscale version configuration information.

[0047] It should be noted that during the process of marking traffic data, failures may occur due to data factors or environmental factors. Therefore, in order to respond promptly to abnormal situations and to check whether the gray-scale version configuration information can be used normally, the gray-scale traffic data after gray-scale marking can be monitored. That is, test metrics of the gray-scale traffic data after gray-scale marking can be obtained in real time through target test cases. These test metrics are used to describe the running status of the target application and can specifically include: error rate, response time, resource consumption (CPU / memory), etc.

[0048] To determine whether the test metrics are normal, a corresponding preset value range can be set for the test metrics. When the test metrics are within the corresponding preset value range, it means that the current target application is running without any abnormalities. In other words, the gray-scale version configuration information is not abnormal, so the current test results indicate that the gray-scale version configuration information is not abnormal.

[0049] In some embodiments, when a test metric is detected to be outside a preset value range, the updated grayscale version configuration information is rolled back according to the online version configuration information.

[0050] It should be noted that if a test metric is detected to be outside the corresponding preset value range, it indicates an anomaly in the current test metric, reflecting an abnormality in the target application's operation. This may be due to an error in the gray-scale version configuration information. Therefore, gray-scale marking of traffic data will cease, and the current gray-scale marking of traffic data will be deleted, essentially restoring the gray-scale traffic data to its original normal traffic data. Additionally, if the gray-scale version configuration information is abnormal, it may be due to an error in the configuration update content. Therefore, while the online version configuration information will be updated, a rollback mechanism will be used to delete the updated content of the gray-scale version configuration information, restoring the gray-scale version configuration information to its state before the update.

[0051] In some embodiments, configuration update content can also be deleted and update error information can be output.

[0052] If the test metric is not within the corresponding preset value range, it indicates that there may be a problem with the configuration update content. Therefore, the configuration update content can be deleted to obtain new configuration update content. At the same time, update exception information is output to indicate that there is an abnormal situation in the current configuration information update process, which facilitates the operation and maintenance personnel to troubleshoot in a timely manner.

[0053] 208. When the test results indicate that there are no abnormalities in the grayscale version configuration information, synchronize the grayscale version configuration information to the online version configuration information of the target application to update the online version configuration information of the target application stored in the cloud platform.

[0054] In this embodiment, the description of step 208 is the same as the detailed description of step 104 in the above embodiments, and will not be repeated in this embodiment.

[0055] 209. When the online version configuration information update is detected to be complete, delete the grayscale markers present in the grayscale traffic data of the target application.

[0056] In this embodiment of the application, during the process of updating the online version configuration information, the update progress can be monitored in real time and recorded as the second update progress. The initial progress of the second update progress is zero, and the final progress to be reached is 100%, indicating that the update is complete. At this time, it can be considered that all configuration information has been updated. Therefore, it is no longer necessary to mark the allocation of traffic. Since the proportion of gray traffic data with gray marking has been continuously increased to 100% when marking traffic data, the gray marking in the gray traffic data can be deleted after the configuration update is completed, that is, all gray traffic data is restored to normal traffic data.

[0057] 210. Delete the process lock corresponding to the configuration update content.

[0058] In this embodiment of the application, once all configuration information has been updated, the current configuration task is considered to be finished, and other tasks can then be executed. Therefore, the process lock corresponding to the configuration update content can be deleted.

[0059] In some embodiments, an update completion message may also be output to indicate that the update is complete.

[0060] 211. When the target application receives traffic data marked with grayscale, it configures the data using the updated grayscale version configuration information.

[0061] In this embodiment of the application, after the configuration information is updated, the configuration can be performed according to the updated configuration information. Since the upstream routing has split the traffic data, that is, it has performed gray-scale marking on a part of the traffic, the application through which the gray-scale marked traffic data flows can also be considered to have been gray-scale marked. Therefore, if the target application receives gray-scale marked traffic data, it can be configured using the updated gray-scale version configuration information.

[0062] 212. When the target application does not receive traffic data marked with grayscale, configure it using the updated online version configuration information.

[0063] In this embodiment of the application, after the configuration information is updated, the configuration can be performed according to the updated configuration information. Since the upstream routing has split the traffic data, that is, it has gray-scale marked a part of the traffic, the application through which the gray-scale marked traffic data flows can also be considered to have been gray-scale marked. Therefore, if the target application does not receive the gray-scale marked traffic data and only receives the normal traffic, it can be configured according to the updated online version configuration information.

[0064] In some embodiments, such as Figure 3 The diagram shows the architecture of the configuration update system. The configuration platform can be used to update configuration information; for example, users can modify configuration information on the platform. After the configuration information is modified, it needs to be published to the nodes, which can be done through the publishing platform. The configuration center is the configuration center within the nodes, storing online and canary versions of the configuration. The routing platform can be considered the upstream route of the nodes; canary marking of traffic is performed by the routing platform, which distributes normal traffic and canary traffic respectively. The online service can be used to configure the configuration information, selecting different configuration information to update based on different traffic received. Normal traffic corresponds to the online configuration, and canary traffic corresponds to the canary configuration.

[0065] The configuration update method proposed in this application stores configuration files in both grayscale and online versions. It first updates the grayscale configuration information in the local cache, and only updates the online version configuration information if no anomalies are detected in the grayscale configuration information using grayscale-marked traffic data. Since only the modified content in the configuration information is updated, and it does not need to be packaged and released with the executable file, configuration updates no longer require program restarts, reducing the overhead of algorithm configuration modification and improving configuration update efficiency. Furthermore, updating the grayscale configuration information locally first and performing anomaly detection through grayscale-marked traffic ensures that the subsequent update process of the online version configuration information will not fail, and the application can still run normally after the online version configuration information is updated, thus satisfying the security of configuration release.

[0066] like Figure 4 As shown in the figure, this application embodiment provides a configuration update device, which may include: The acquisition module 401 is used to acquire configuration update content, which indicates the content that needs to be modified in the configuration file for the target application. The processing module 402 is used to update the grayscale version configuration information in the cloud platform and update the grayscale version configuration information cached locally in the target application according to the configuration update content. The processing module 402 is also used to load the gray version configuration information through the target application when the gray version configuration information is detected to be updated, and to run the target application after loading through the target test cases to obtain the test results. The target test cases are configured with gray version configuration information. The processing module 402 is also used to synchronize the grayscale version configuration information to the online version configuration information of the target application when the test result indicates that there is no abnormality in the grayscale version configuration information, so as to update the online version configuration information of the target application stored in the cloud platform.

[0067] In some embodiments, the processing module 402 is further configured to perform grayscale marking on the traffic data of the target application; The processing module 402 is specifically used to collect grayscale traffic data of the target application and test the target application based on the grayscale traffic data through the target test cases to obtain test results; the grayscale traffic data is traffic data that has been grayscale-tagged.

[0068] In some embodiments, the processing module 402 is further configured to delete the grayscale markers present in the grayscale traffic data of the target application when the online version configuration information update is detected to be complete.

[0069] In some embodiments, the acquisition module 401 is specifically used to acquire test metrics of grayscale traffic data in real time through target test cases during the operation of the target application. The test metrics are used to describe the running status of the target application. The processing module 402 is specifically used to determine that there is no abnormality in the grayscale version configuration information when the test indicator is detected to be within the preset value range.

[0070] In some embodiments, the processing module 402 is further configured to, when it is detected that the test metric is not within a preset value range, perform data rollback on the updated grayscale version configuration information according to the online version configuration information.

[0071] In some embodiments, the processing module 402 is further configured to configure the target application by means of the updated grayscale version configuration information when the target application receives grayscale-marked traffic data; The processing module 402 is also used to configure the target application using the updated online version configuration information when the target application does not receive grayscale-marked traffic data.

[0072] In some embodiments, the processing module 402 is further configured to detect whether there are any tasks in the task publishing list that are in the publishing state; Processing module 402 is also used to add a process lock for configuration update content when it is detected that no task is in the publishing state; The processing module 402 is also used to delete the process lock corresponding to the configuration update content when it is detected that the online version configuration information update is complete.

[0073] In this embodiment, each module can implement the configuration update method provided in the above method embodiments and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0074] like Figure 5 As shown in the embodiments of this application, a control terminal is also provided, which may include: Memory 501 storing executable program code; Processor 502 coupled to memory 501; Specifically, the processor 502 calls the executable program code stored in the memory 501 to execute the configuration update method executed by the control terminal in the above method embodiments.

[0075] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the configuration update method in the above-described method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0076] This application also provides a computer program product, which stores a computer program. When the computer program is executed by a processor, it implements the various processes of the configuration update method in the above method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0077] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program code.

[0078] It should be understood, in the several embodiments provided in this application, that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative; for example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0079] In this application, the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0080] In this application, memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0081] In this application, those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. This program can be stored in a computer-readable storage medium, including permanent and non-permanent, removable and non-removable storage media. The storage medium can implement information storage by any method or technology, and the information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), other types of random access memory (RAM), read-only memory (ROM), one-time programmable read-only memory (OTPROM), electrically-erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information that can be accessed by a computing device. As defined in this document, computer-readable media do not include transient media, such as modulated data signals and carrier waves.

[0082] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the term "comprising" or any other variations thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0083] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application. The above-mentioned multiple embodiments are not necessarily multiple independent embodiments; they are divided into multiple embodiments only to highlight different technical features in different embodiments. Those skilled in the art should understand that the above-mentioned multiple embodiments can also be combined arbitrarily.

[0084] In the various embodiments of this application, it should be understood that the sequence number of each process does not necessarily imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0085] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; they can be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0086] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0087] If the integrated units described above are implemented as software functional units and sold or used as independent products, they can be stored in a computer-accessible memory. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several requests to cause a computer device (which can be a personal computer, server, or network device, specifically a processor in the computer device) to execute some or all of the steps of the methods described in the various embodiments of this application.

[0088] The above are merely specific embodiments of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to these embodiments, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A configuration update method, characterized in that, Applied to a control terminal, the method includes: Obtain configuration update content, which indicates the content that needs to be modified in the configuration file for the target application; Based on the configuration update content, update the grayscale version configuration information in the cloud platform, and update the grayscale version configuration information cached locally in the target application; When the grayscale version configuration information update is detected, the grayscale version configuration information is loaded through the target application, and the loaded target application is run and tested through the target test case to obtain the test results. The target test case is configured with the grayscale version configuration information. When the test results indicate that there are no abnormalities in the grayscale version configuration information, the grayscale version configuration information is synchronized to the online version configuration information of the target application to update the online version configuration information of the target application stored in the cloud platform.

2. The method according to claim 1, characterized in that, Before loading the grayscale version configuration information through the target application, the method further includes: The traffic data of the target application is grayscale-marked; The step of running tests on the loaded target application using target test cases to obtain test results includes: Collect grayscale traffic data of the target application, and test the target application based on the grayscale traffic data using the target test cases to obtain the test results; the grayscale traffic data is traffic data that has been grayscale-tagged.

3. The method according to claim 2, characterized in that, When the test result indicates that the grayscale version configuration information is not abnormal, the grayscale version configuration information is synchronized to the online version configuration information of the target application to update the online version configuration information of the target application stored in the cloud platform. The method further includes: When the online version configuration information update is detected to be complete, the grayscale markers present in the grayscale traffic data of the target application are deleted.

4. The method according to claim 2, characterized in that, The test results obtained by testing the target application using target test cases based on the grayscale traffic data include: During the operation of the target application, test metrics of the grayscale traffic data are obtained in real time through the target test cases. These test metrics are used to describe the running status of the target application. When the test metric is detected to be within a preset value range, it is determined that the test result indicates that the grayscale version configuration information is not abnormal.

5. The method according to claim 4, characterized in that, After obtaining the test metrics of the grayscale traffic data in real time through the target test cases, the method further includes: When the test metric is detected to be outside the preset value range, the updated grayscale version configuration information is rolled back according to the online version configuration information.

6. The method according to claim 2, characterized in that, When the test result indicates that the grayscale version configuration information is not abnormal, the grayscale version configuration information is synchronized to the online version configuration information of the target application to update the online version configuration information of the target application stored in the cloud platform. The method further includes: When the target application receives traffic data marked in grayscale, it configures itself using the updated grayscale version configuration information; When the target application does not receive grayscale-marked traffic data, it is configured using the updated online version configuration information.

7. The method according to claim 1, characterized in that, Before updating the grayscale version configuration information in the cloud platform according to the configuration update content, and updating the grayscale version configuration information cached locally in the target application, the method further includes: Check if any tasks in the published list are currently in the published state. When no task in the publishing state is detected, a process lock is added to the configuration update content; When the test result indicates that the grayscale version configuration information is not abnormal, the grayscale version configuration information is synchronized to the online version configuration information of the target application to update the online version configuration information of the target application stored in the cloud platform. The method further includes: When the online version configuration information update is detected to be complete, the process lock corresponding to the configuration update content is deleted.

8. A configuration update device, characterized in that, The device, configured in a control terminal, includes: The acquisition module is used to acquire configuration update content, which indicates the content that needs to be modified in the configuration file of the target application; The processing module is used to update the grayscale version configuration information in the cloud platform according to the configuration update content, and update the grayscale version configuration information cached locally in the target application; The processing module is further configured to, when detecting that the grayscale version configuration information has been updated, load the grayscale version configuration information through the target application, and run the loaded target application through the target test case to obtain the test result, wherein the target test case is configured with the grayscale version configuration information; The processing module is further configured to synchronize the grayscale version configuration information to the online version configuration information of the target application when the test result indicates that there is no abnormality in the grayscale version configuration information, so as to update the online version configuration information of the target application stored in the cloud platform.

9. A control terminal, characterized in that, include: Memory containing executable program code; and the processor coupled to the memory; The processor invokes the executable program code stored in the memory to execute the configuration update method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, include: The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the configuration update method as described in any one of claims 1 to 7.

Images