Apollo configuration version processing method, device and system

Abstract

This application provides a method, apparatus, and system for processing Apollo configuration versions. The method is applied to a production server; it obtains Apollo configuration version files based on a message queue; the Apollo configuration version file includes: new version configuration information and a change list; the message queue stores file identifiers for the test server to package and push the Apollo configuration version file submitted by the user for testing; it performs a configuration comparison operation based on the new version configuration information and the change list, and sends the configuration comparison results to the terminals of relevant personnel for subsequent modification or release operations. After the user submits an Apollo configuration version for testing through the test server, it can automatically trigger the production server to perform a pre-configuration comparison, which can effectively avoid configuration version release failure on the production server, thereby affecting the stability and reliability of the system and avoiding asset losses.

Description

Technical Field

[0001] This application relates to the field of software technology, and in particular to a method, apparatus and system for processing Apollo configuration versions. Background Technology

[0002] As software products upgrade and iterate at an increasingly rapid pace, the requirements for software stability testing are becoming increasingly stringent. This necessitates servers with extremely high stability, capable of continuously providing services and maintaining reliability. Anomalies during version testing can lead to server failures, which in turn can severely impact system stability.

[0003] In existing banking systems, due to security compliance policies, the testing environment cannot access the production environment. As a result, Apollo configuration comparison can only be performed during version testing. This late intervention point can block the entire testing process after a problem occurs, requiring a rollback of the entire R&D process, affecting the current development progress, and potentially causing test anomalies or production accidents, resulting in asset losses. Summary of the Invention

[0004] The purpose of this application is to provide a method, apparatus and system for processing Apollo configuration versions. After a user submits an Apollo configuration version for testing through a test server, it can automatically trigger a pre-configuration comparison on a production server. This can effectively prevent the Apollo configuration version from failing to be released on the production server, thereby affecting the stability and reliability of the system and avoiding asset losses.

[0005] In a first aspect, embodiments of this application provide a method for processing Apollo configuration versions, which is applied to a production server. The method includes: obtaining an Apollo configuration version file based on a message queue; the Apollo configuration version file includes: new version configuration information and a change list; the message queue stores a file identifier that the test server packages and pushes after receiving the Apollo configuration version file to be tested submitted by the user; performing a configuration comparison operation based on the new version configuration information and the change list, and sending the configuration comparison result to the terminal corresponding to the relevant staff so that the relevant staff can perform subsequent modification or release operations.

[0006] In a preferred embodiment of this application, the step of obtaining the Apollo configuration version file based on the message queue includes: extracting the corresponding data packet according to the file identifier in the message queue; parsing the data packet to obtain the Apollo configuration version file.

[0007] In a preferred embodiment of this application, a Git repository is set up on the production server; the step of performing a configuration comparison operation based on the new version configuration information and the change list includes: performing a first comparison between the new version configuration information and the current version configuration information in the Git repository to determine the changes; and performing a second comparison between the changes and the change list to determine the configuration comparison result.

[0008] In a preferred embodiment of this application, both the new version configuration information and the current version configuration information include configuration information corresponding to multiple configuration files. The step of performing a first comparison between the new version configuration information and the current version configuration information in the Git repository to determine the changes includes: for each new configuration file in the new version configuration information, searching for a current configuration file with the same filename in the current version configuration information in the Git repository; comparing the configuration information corresponding to the new configuration file and the current configuration file respectively to obtain the current comparison result; and determining the changes based on the comparison results corresponding to the multiple new configuration files respectively.

[0009] In a preferred embodiment of this application, the aforementioned Apollo configuration version file also carries the communication information of relevant personnel; the step of sending the configuration comparison result to the terminal corresponding to the relevant personnel includes: if the configuration comparison result is consistent, sending a test success message to the terminal corresponding to the communication information; if the configuration comparison result is inconsistent, sending a test failure message and inconsistent change items to the terminal corresponding to the communication information.

[0010] Secondly, this application also provides a method for processing Apollo configuration versions, which is applied to a test server. The method includes: receiving an Apollo configuration version file to be tested submitted by a user; the Apollo configuration version file includes: new version configuration information and a change list; packaging the Apollo configuration version file and asynchronously pushing it to a message queue, so that the production server can obtain the Apollo configuration version file based on the message queue, perform a configuration comparison operation based on the new version configuration information and the change list, and send the configuration comparison result to the terminal corresponding to the relevant staff so that the relevant staff can perform subsequent modification or release operations.

[0011] Thirdly, this application also provides an Apollo configuration version processing device, which is applied to a production server; the device includes: a file acquisition module, used to acquire an Apollo configuration version file based on a message queue; the Apollo configuration version file includes: new version configuration information and a change list; the message queue stores a file identifier that the test server packages and pushes after receiving the Apollo configuration version file to be tested submitted by the user; a configuration comparison module, used to perform configuration comparison operations based on the new version configuration information and the change list; and a result sending module, used to send the configuration comparison results to the terminals corresponding to relevant personnel, so that relevant personnel can perform subsequent modification or release operations.

[0012] Fourthly, this application also provides an Apollo configuration version processing device, which is applied to a test server; the device includes: a file receiving module, used to receive an Apollo configuration version file to be tested submitted by a user; the Apollo configuration version file includes: new version configuration information and a change list; a packaging and pushing module, used to package the Apollo configuration version file and asynchronously push it to a message queue, so that the production server can obtain the Apollo configuration version file based on the message queue, perform a configuration comparison operation based on the new version configuration information and the change list, and send the configuration comparison result to the terminal corresponding to the relevant staff so that the relevant staff can perform subsequent modification or release operations.

[0013] Fifthly, embodiments of this application also provide an Apollo configuration version processing system, the system including a test server and a production server; the test server is used to execute the Apollo configuration version processing method as described in the second aspect; the production server is used to execute the Apollo configuration version processing method as described in the first aspect.

[0014] In a sixth aspect, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are invoked and executed by a processor, the computer-executable instructions cause the processor to implement the methods described in the first and second aspects above.

[0015] The Apollo configuration version processing method, apparatus, and system provided in this application, applied to a production server, include: obtaining an Apollo configuration version file based on a message queue; the Apollo configuration version file includes: new version configuration information and a change list; the message queue stores a file identifier that the test server packages and pushes after receiving the Apollo configuration version file submitted by the user for testing; performing a configuration comparison operation based on the new version configuration information and the change list, and sending the configuration comparison result to the terminal corresponding to the relevant personnel so that the relevant personnel can perform subsequent modification or release operations. Through the above method, after a user submits an Apollo configuration version for testing through the test server, this application embodiment can automatically trigger a pre-configuration comparison on the production server, effectively avoiding the failure of Apollo configuration version release on the production server, thereby affecting the stability and reliability of the system and preventing asset losses. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0017] Figure 1 A flowchart illustrating a method for processing Apollo configuration versions provided in this application embodiment;

[0018] Figure 2 A flowchart illustrating another Apollo configuration version processing method provided in this application embodiment;

[0019] Figure 3 A schematic diagram illustrating a processing method for an Apollo configuration version provided in an embodiment of this application;

[0020] Figure 4 A flowchart illustrating another Apollo configuration version processing method provided in this application embodiment;

[0021] Figure 5 A structural block diagram of a processing device with an Apollo configuration version provided in this application embodiment;

[0022] Figure 6 A structural block diagram of another Apollo configuration version of the processing device provided in the embodiments of this application;

[0023] Figure 7 This is a processing system architecture diagram of an Apollo configuration version provided in an embodiment of this application. Detailed Implementation

[0024] The technical solutions of this application will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] Under the guidance of security and compliance policies, the current banking system does not allow the test environment to access the production environment. This means that Apollo configuration comparison can only be performed during version testing. The intervention point is too late, which will block the progress of the entire testing process after a problem occurs. It is necessary to roll back the entire R&D process, which will affect the current development progress and may cause test anomalies or production accidents, resulting in asset losses.

[0026] Based on this, this application provides a method, apparatus and system for processing Apollo configuration versions. After a user submits an Apollo configuration version for testing through a test server, it can automatically trigger a pre-configuration comparison on a production server. This can effectively prevent the Apollo configuration version from failing to be released on the production server, thereby affecting the stability and reliability of the system and avoiding asset losses.

[0027] To facilitate understanding of this embodiment, a method for configuring an Apollo version disclosed in this application embodiment will first be described in detail.

[0028] Figure 1 A flowchart illustrating an Apollo configuration version processing method provided in this application embodiment, the method being applied to a production server; the method specifically includes the following steps:

[0029] Step S102: Obtain the Apollo configuration version file based on the message queue; the Apollo configuration version file includes: new version configuration information and change list; the message queue stores the file identifier that the test server packages and pushes after receiving the Apollo configuration version file to be tested submitted by the user.

[0030] In this step, after the user submits the Apollo configuration version file to be tested through the test server, the test server will automatically package it and push it asynchronously to the message queue, that is, add the file identifier to the message queue. The production server will consume the message queue, and when it is time to process the file identifier, it will retrieve the Apollo configuration version file based on the file identifier.

[0031] The aforementioned test server can be any server capable of development and testing, such as the Starlink platform. This platform is an integrated development and operations platform that provides one-stop R&D and operations services, covering the entire software development lifecycle from requirement submission, development management, test management, application release management, and performance statistics management. It provides a unified perspective, unified standards, and unified processes, connects the toolchains of each stage, integrates the CI / CD pipeline, enhances the automation capabilities of each stage, and realizes a panoramic view of the end-to-end value stream for users.

[0032] Step S104: Perform a configuration comparison operation based on the new version configuration information and change list, and send the configuration comparison results to the terminals of the relevant staff so that the relevant staff can make subsequent modifications or release operations.

[0033] After obtaining the Apollo configuration version file, a configuration comparison operation is performed based on the new version configuration information and change list in the file, as well as the current version configuration information in the corresponding repository on the production server, to determine the configuration comparison result.

[0034] The configuration comparison results, whether successful or unsuccessful, are sent to the relevant staff so that they can make timely corrections in the event of a failure or perform subsequent publishing operations in the event of a success.

[0035] The Apollo configuration version processing method provided in this application first obtains the Apollo configuration version file based on a message queue. The Apollo configuration version file includes new version configuration information and a change list. The message queue stores a file identifier that the test server packages and pushes after receiving the Apollo configuration version file submitted by the user for testing. A configuration comparison operation is performed based on the new version configuration information and the change list, and the configuration comparison result is sent to the terminal corresponding to the relevant personnel so that they can perform subsequent modifications or release operations. Through the above method, after the user submits the Apollo configuration version for testing through the test server, this application embodiment can automatically trigger the production server to perform a pre-configuration comparison, enabling relevant personnel to take appropriate actions based on the comparison results. This effectively avoids the Apollo configuration version failing to be released on the production server, thereby affecting the stability and reliability of the system and preventing asset losses.

[0036] This application also provides a method for processing Apollo configuration versions, which is implemented based on the previous embodiment. This embodiment focuses on describing the file acquisition process and the configuration comparison process.

[0037] See Figure 2 As shown, the entire file acquisition process and configuration comparison process are as follows:

[0038] Step S202: Extract the corresponding data packet based on the file identifier in the message queue. See also... Figure 3 As shown, the file identifier here can be a data packet address, such as a zip address; when the production server consumes the message queue, it can download the zip data packet based on the zip address.

[0039] Step S204: Parse the data packet to obtain the Apollo configuration version file. As in the example above, after parsing the zip data packet, the Apollo configuration version file can be obtained. This file includes the new version configuration information and the corresponding change list.

[0040] The directory structure of the Apollo configuration version files mentioned above is shown in Table 1:

[0041] Table 1

[0042]

[0043]

[0044] As shown above, the file can also include a deploy.config.properties file, which provides flexible configuration options for the corresponding application project, leaving flexible interface parameters for subsequent extended functions.

[0045] The aforementioned production server also has a Git repository set up; step S206, compare the new version configuration information with the current version configuration information in the Git repository to determine the changes;

[0046] Both the new version configuration information and the current version configuration information include configuration information corresponding to multiple configuration files;

[0047] (1) For each new configuration file in the new version configuration information, find the current configuration file with the same file name in the current version configuration information in the Git repository;

[0048] (2) Compare the configuration information corresponding to the new configuration file and the current configuration file respectively to obtain the current comparison result;

[0049] (3) Determine the change items based on the comparison results corresponding to the multiple new configuration files respectively.

[0050] Specifically, the key and value in each new configuration file can be read and compared with the key and value in the current configuration file with the same filename to obtain the change items. Change items are generated based on the discrepancies. These change items include whether a specific key in a file is in a new, deleted, or updated state.

[0051] Step S208: Perform a second comparison between the changed items and the change list to determine the configuration comparison result.

[0052] By comparing the changes identified in the above comparison with the change list in the Apollo configuration version file, the comparison results can be further determined. For example... Figure 3 As shown, the change list content in the apollo.release.json file in the zip data package is read, and the above change items (i.e., the summary result) are compared with the change list content to determine whether they are consistent.

[0053] Step S210: If the configuration comparison result is consistent, a test success message is sent to the terminal corresponding to the communication information; if the configuration comparison result is inconsistent, a test failure message and inconsistent change items are sent to the terminal corresponding to the communication information.

[0054] In practice, the Apollo configuration version file can also include the communication information of relevant personnel, such as mobile phone numbers and email addresses. After the production server determines the configuration comparison results, regardless of whether the results are consistent, it will send the comparison results to the terminal corresponding to the communication information. This allows relevant personnel to understand the specific situation of their files to be tested in a timely manner. If inconsistencies exist, timely modifications can be made. This can solve some pain points of Apollo configuration version release anomalies and effectively prevent Apollo configuration release from causing production release failures, thereby affecting the stability and reliability of the system, and in severe cases, causing financial losses.

[0055] In the Apollo configuration version processing method provided in this application embodiment, the addition, deletion, and modification of Apollo configurations can be compared during testing, exposing potential problems in advance. For example, information can be sent to the relevant responsible persons and personnel via email, allowing the development manager to identify and resolve issues beforehand. This avoids omissions and inconsistencies in configuration during release, preventing online bugs or release delays. Furthermore, a final comparison mechanism is implemented during the release phase as a fallback, effectively preventing production accidents and financial losses.

[0056] Based on the above method embodiments, this application also provides a method for processing Apollo configuration versions, which is applied to a test server; see [link to related documentation]. Figure 4 As shown, the method specifically includes the following steps:

[0057] Step S402: Receive the Apollo configuration version file to be tested submitted by the user; the Apollo configuration version file includes: new version configuration information and change list;

[0058] Step S404: Package the Apollo configuration version file and push it asynchronously to the message queue so that the production server can obtain the Apollo configuration version file based on the message queue, perform a configuration comparison operation based on the new version configuration information and change list, and send the configuration comparison results to the terminals of relevant staff so that relevant staff can perform subsequent modification or release operations.

[0059] In the above manner, after a user submits an Apollo configuration version for testing through the test server, this application embodiment can automatically trigger the production server to perform a pre-configuration comparison, so that relevant personnel can take appropriate actions based on the comparison results, effectively avoiding the failure of Apollo configuration version release on the production server, thereby affecting the stability and reliability of the system and avoiding asset losses.

[0060] The method provided in this application embodiment has the same implementation principle and technical effect as the aforementioned method embodiment on the production server side. For the sake of brevity, any parts of the method embodiment not mentioned can be referred to the corresponding content in the aforementioned method embodiment.

[0061] Based on the above-described method embodiments on the production server side, this application also provides an Apollo configuration version processing device, which is applied to a production server; see also Figure 5 As shown, the device includes:

[0062] The file acquisition module 52 is used to acquire the Apollo configuration version file based on the message queue. The Apollo configuration version file includes: new version configuration information and change list. The message queue stores the file identifier that the test server packages and pushes after receiving the Apollo configuration version file to be tested submitted by the user. The configuration comparison module 54 is used to perform configuration comparison operations based on the new version configuration information and change list. The result sending module 56 is used to send the configuration comparison results to the terminals of relevant personnel so that relevant personnel can make subsequent modifications or release operations.

[0063] In a preferred embodiment of this application, the file acquisition module 52 is used to extract the corresponding data packet according to the file identifier in the message queue; and to parse the data packet to obtain the Apollo configuration version file.

[0064] In a preferred embodiment of this application, a Git repository is built on the production server; the configuration comparison module 54 is used to perform a first comparison between the new version configuration information and the current version configuration information in the Git repository to determine the changes; and to perform a second comparison between the changes and the change list to determine the configuration comparison result.

[0065] In a preferred embodiment of this application, both the new version configuration information and the current version configuration information include configuration information corresponding to multiple configuration files respectively; the configuration comparison module 54 is used to search for the current configuration file with the same file name in the current version configuration information in the Git repository for each new configuration file in the new version configuration information; compare the configuration information corresponding to the new configuration file and the current configuration file respectively to obtain the current comparison result; and determine the change items based on the comparison results corresponding to multiple new configuration files respectively.

[0066] In a preferred embodiment of this application, the Apollo configuration version file also carries the communication information of relevant personnel; the result sending module 56 is used to send test success information to the terminal corresponding to the communication information if the configuration comparison result is consistent; and to send test failure information and inconsistent change items to the terminal corresponding to the communication information if the configuration comparison result is inconsistent.

[0067] The device provided in this application embodiment has the same implementation principle and technical effect as the aforementioned method embodiment on the production server side. For the sake of brevity, any parts of the device embodiment not mentioned can be referred to the corresponding content in the aforementioned method embodiment.

[0068] Based on the above-described method embodiments on the test server side, this application also provides a processing device for an Apollo configuration version, which is applied to a test server; see also Figure 6 As shown, the device includes:

[0069] The file receiving module 62 is used to receive the Apollo configuration version file to be tested submitted by the user. The Apollo configuration version file includes: new version configuration information and change list. The packaging and pushing module 64 is used to package the Apollo configuration version file and push it asynchronously to the message queue, so that the production server can obtain the Apollo configuration version file based on the message queue, perform configuration comparison operation based on the new version configuration information and change list, and send the configuration comparison result to the terminal of the relevant staff so that the relevant staff can perform subsequent modification or release operations.

[0070] Through the modules in the Apollo configuration version processing device described above, this embodiment of the application can automatically trigger the production server to perform pre-configuration comparison after the user submits the Apollo configuration version for testing through the test server. This enables relevant personnel to take appropriate actions based on the comparison results, effectively preventing the Apollo configuration version from failing to be released on the production server, thereby affecting the stability and reliability of the system and avoiding asset losses.

[0071] The device provided in this application embodiment has the same implementation principle and technical effect as the aforementioned method embodiment on the production server side. For the sake of brevity, any parts of the device embodiment not mentioned can be referred to the corresponding content in the aforementioned method embodiment.

[0072] Based on the above method embodiments, this application also provides an Apollo configuration version processing system, which includes a test server and a production server; the test server is used to execute the Apollo configuration version processing method as described in the second embodiment; the production server is used to execute the Apollo configuration version processing method as described in the first embodiment.

[0073] See Figure 7 The system architecture diagram shown illustrates that, in this embodiment, after a project version is submitted for testing, an Apollo configuration comparison is automatically triggered. The production server verifies, based on given rules, what additions, modifications, and deletions have been made to the Apollo configuration items in this version of the project. These changes to the Apollo configuration items are then compared and verified against the expected modifications provided by the corresponding developers and responsible parties. The verification results are promptly pushed to relevant personnel, thereby preventing omissions and inconsistencies in configuration during release, which could lead to online bugs or version release delays.

[0074] The system provided in this application embodiment has the same implementation principle and technical effects as the aforementioned method embodiment. For the sake of brevity, any parts not mentioned in the system embodiment can be referred to the corresponding content in the aforementioned method embodiment.

[0075] This application also provides a computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are invoked and executed by a processor, they cause the processor to implement the following production server-side method:

[0076] The Apollo configuration version file is obtained based on the message queue. The Apollo configuration version file includes: new version configuration information and change list. The message queue stores the file identifier that the test server packages and pushes after receiving the Apollo configuration version file to be tested submitted by the user. The configuration comparison operation is performed based on the new version configuration information and change list, and the configuration comparison results are sent to the corresponding terminals of relevant personnel so that relevant personnel can make subsequent modifications or release operations.

[0077] In a preferred embodiment of this application, the step of obtaining the Apollo configuration version file based on the message queue includes: extracting the corresponding data packet according to the file identifier in the message queue; parsing the data packet to obtain the Apollo configuration version file.

[0078] In a preferred embodiment of this application, a Git repository is set up on the production server; the step of performing a configuration comparison operation based on the new version configuration information and the change list includes: performing a first comparison between the new version configuration information and the current version configuration information in the Git repository to determine the changes; and performing a second comparison between the changes and the change list to determine the configuration comparison result.

[0079] In a preferred embodiment of this application, both the new version configuration information and the current version configuration information include configuration information corresponding to multiple configuration files. The step of performing a first comparison between the new version configuration information and the current version configuration information in the Git repository to determine the changes includes: for each new configuration file in the new version configuration information, searching for a current configuration file with the same filename in the current version configuration information in the Git repository; comparing the configuration information corresponding to the new configuration file and the current configuration file respectively to obtain the current comparison result; and determining the changes based on the comparison results corresponding to the multiple new configuration files respectively.

[0080] In a preferred embodiment of this application, the aforementioned Apollo configuration version file also carries the communication information of relevant personnel; the step of sending the configuration comparison result to the terminal corresponding to the relevant personnel includes: if the configuration comparison result is consistent, sending a test success message to the terminal corresponding to the communication information; if the configuration comparison result is inconsistent, sending a test failure message and inconsistent change items to the terminal corresponding to the communication information.

[0081] It is also used to implement methods on the test server side;

[0082] The system receives Apollo configuration version files submitted by users for testing. These files include new version configuration information and a change list. The system packages the Apollo configuration version files and pushes them asynchronously to a message queue. This allows the production server to retrieve the Apollo configuration version files from the message queue, perform a configuration comparison based on the new version configuration information and change list, and send the comparison results to the terminals of relevant personnel for subsequent modifications or releases.

[0083] For specific implementation details, please refer to the aforementioned method embodiments, which will not be repeated here.

[0084] The computer program products of the methods, apparatus and systems provided in the embodiments of this application include a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0085] Unless otherwise specifically stated, the relative steps, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of this application.

[0086] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0087] In the description of this application, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0088] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the technical scope disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A method for processing Apollo configuration versions, characterized in that, The method is applied to a production server in a banking system that has a Git repository. The method includes: The Apollo configuration version file is obtained based on a message queue; the Apollo configuration version file includes: new version configuration information and a change list; the message queue stores the file identifier that the bank system's test server packages and pushes after receiving the Apollo configuration version file to be tested submitted by the user; The new version configuration information is first compared with the current version configuration information in the Git repository to determine the changes; the changes are then compared with the change list to determine the configuration comparison result, and the configuration comparison result is sent to the terminal of the relevant staff so that the relevant staff can perform subsequent modification or release operations.

2. The method according to claim 1, characterized in that, The steps to obtain the Apollo configuration version file based on the message queue include: Download the corresponding data packet according to the file identifier in the message queue; The data packet is parsed to obtain the Apollo configuration version file.

3. The method according to claim 1, characterized in that, Both the new version configuration information and the current version configuration information include configuration information corresponding to multiple configuration files; the step of comparing the new version configuration information with the current version configuration information in the Git repository to determine the changes includes: For each new configuration file in the new version configuration information, search for the current configuration file with the same filename in the current version configuration information in the Git repository; compare the configuration information corresponding to the new configuration file and the current configuration file respectively to obtain the current comparison result; The changes are determined based on the comparison results corresponding to the various new configuration files.

4. The method according to claim 1, characterized in that, The Apollo configuration version file also carries the communication information of relevant personnel; the step of sending the configuration comparison results to the terminals corresponding to the relevant personnel includes: If the configuration comparison results are consistent, a test success message will be sent to the terminal corresponding to the communication information; If the configuration comparison result is inconsistent, the test failure information and the inconsistent change items will be sent to the terminal corresponding to the communication information.

5. A method for processing Apollo configuration versions, characterized in that, The method is applied to a test server of a banking system; the method includes: Receive the Apollo configuration version file to be tested submitted by the user; the Apollo configuration version file includes: new version configuration information and a change list; The Apollo configuration version file is packaged and asynchronously pushed to a message queue. This allows the production server of the bank system, which has a Git repository, to retrieve the Apollo configuration version file from the message queue. The new version configuration information is then compared with the current version configuration information in the Git repository to identify changes. The changes are then compared with the change list to determine the configuration comparison result. The configuration comparison result is then sent to the terminals of the relevant staff members so that they can perform subsequent modifications or release operations.

6. A processing device with an Apollo configuration version, characterized in that, The device is used on a production server in a banking system that has a Git repository; the device includes: The file acquisition module is used to acquire Apollo configuration version files based on a message queue. The Apollo configuration version files include: new version configuration information and a change list. The message queue stores the file identifiers that the bank system's test server packages and pushes after receiving the Apollo configuration version files to be tested submitted by the user. The configuration comparison module is used to perform a first comparison between the new version configuration information and the current version configuration information in the Git repository to determine the changes; and to perform a second comparison between the changes and the change list to determine the configuration comparison result. The result sending module is used to send the configuration comparison results to the terminals of the relevant staff members so that the relevant staff members can make subsequent modifications or release operations.

7. A processing device with an Apollo configuration version, characterized in that, The device is used in a test server of a banking system; the device includes: The file receiving module is used to receive Apollo configuration version files submitted by users for testing; the Apollo configuration version files include: new version configuration information and a change list; The packaging and push module is used to package the Apollo configuration version file and asynchronously push it to a message queue. This allows the production server of the bank system, which has a Git repository, to retrieve the Apollo configuration version file from the message queue. The new version configuration information is then compared with the current version configuration information in the Git repository to identify changes. The changes are then compared with the change list to determine the configuration comparison result. The configuration comparison result is then sent to the terminals of relevant staff members so that they can perform subsequent modifications or release operations.

8. A processing system with an Apollo configuration version, characterized in that, The system includes a test server for the banking system and a production server with a Git repository; the test server is used to execute the processing method of the Apollo configuration version as described in claim 5. The production server is used to execute the processing method of any one of the Apollo configuration versions as described in claims 1-4.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when invoked and executed by a processor, cause the processor to perform the method described in any one of claims 1 to 5.

Images