Method and apparatus for processing application version parameter, electronic device, and storage medium

Abstract

The application discloses a processing method and device of application version parameters, electronic equipment and storage medium, which can be applied to the distributed field or the financial field, and the method comprises the steps of obtaining a user-imported software package to be processed; analyzing the software package to be processed to obtain to-be-customized parameters corresponding to each module in the software package to be processed; creating a deployment task of the software package to be processed in response to a task creation operation of a user; calculating each to-be-customized parameter by using a pre-set calculation method to obtain a plurality of calculation parameter values; distributing each calculation parameter value to a corresponding copy according to the type of each calculation parameter value to obtain a customized parameter list of each copy; generating a current executable job flow according to the installation method of each module; executing the current executable job flow to deploy each copy and batch-replacing corresponding parameters in configuration files of each copy of each module according to the customized parameter list of each copy.

Description

Technical Field

[0001] This application relates to the field of product deployment technology, and in particular to a method and apparatus for processing application version parameters, an electronic device, and a storage medium. Background Technology

[0002] In large enterprises such as banks, version control is usually done by "product". Each product includes multiple modules. The product automatically packages the artifacts of multiple modules to generate a product-level "package", which is then submitted to the version repository.

[0003] Currently, the deployment of software packages mainly involves relevant personnel operating various tools to parse the software packages in the version control system, and then deploying the modules and customizing the parameters within the software packages.

[0004] However, the software package is quite complex and contains many modules, and it also needs to be deployed on large-scale servers. Therefore, deploying the software package manually is relatively slow. Summary of the Invention

[0005] In view of the shortcomings of the prior art, this application provides a method and apparatus for processing application version parameters, an electronic device, and a storage medium to solve the problem of relatively low efficiency in the prior art.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] The first aspect of this application provides a method for processing application version parameters, including:

[0008] Retrieve the user-imported software packages to be processed;

[0009] The software package to be processed is parsed to obtain the customization parameters corresponding to each module in the software package;

[0010] In response to the user's task creation operation, a deployment task for the pending software package is created;

[0011] Using a pre-set calculation method, each of the parameters to be customized is calculated to obtain multiple calculated parameter values;

[0012] Based on the type of each calculated parameter value, each calculated parameter value is distributed to the corresponding replica to obtain a customized parameter list for each replica;

[0013] Based on the installation method of each module, generate the current executable job flow;

[0014] The currently executable job flow is executed to deploy each of the replicas, and the corresponding parameters in the configuration files of each of the replicas of each module are replaced in batches according to the customized parameter list of each of the replicas.

[0015] Optionally, in the above-described method for processing application version parameters, the step of using a pre-set calculation method to calculate each of the parameters to be customized, obtaining multiple calculated parameter values, including:

[0016] For each of the parameters to be customized, based on the keyword of the parameter to be customized, query whether the calculation method type corresponding to the parameter to be customized is template-first;

[0017] If the query finds that the calculation method type corresponding to the parameter to be customized is template priority, then query whether the calculation parameter value corresponding to the parameter to be customized exists in the parameter configuration center;

[0018] If the calculated parameter value corresponding to the parameter to be customized exists in the parameter configuration center, then the calculated parameter value corresponding to the parameter to be customized is returned.

[0019] If the query finds that the calculation method type corresponding to the parameter to be customized is not template priority, or if the query finds that the calculation parameter value corresponding to the parameter to be customized does not exist in the parameter configuration center, then the SQL statement associated with the calculation method identifier corresponding to the parameter to be customized and the method input parameters are retrieved.

[0020] Based on the SQL statement and the method parameters, the calculated parameter value corresponding to the parameter to be customized is obtained.

[0021] Optionally, in the above method for processing application version parameters, the step of distributing each calculated parameter value to a corresponding replica according to the type of each calculated parameter value to obtain a customized parameter list for each replica includes:

[0022] For each of the calculated parameter values, if the calculated parameter value is a product-level parameter, then the calculated parameter value is distributed to each of the replicas of each module to obtain a customized parameter list for each replica.

[0023] If the calculated parameter value is a module-level parameter, then the calculated parameter value is distributed to each copy of the module to which it belongs, so as to obtain a customized parameter list for each copy.

[0024] If the calculated parameter value is a replica-level parameter, then the calculated parameter value is distributed to the corresponding replica to obtain a list of customized parameters for the replica.

[0025] Optionally, in the above method for processing application version parameters, generating the current executable job flow based on the installation method of each module includes:

[0026] For each module, obtain the installation method for that module based on its type;

[0027] Replace the parameters of each command module in the module installation method to obtain the current executable job flow corresponding to the module.

[0028] Optionally, in the above method for processing application version parameters, the step of executing the currently executable job flow to deploy each of the replicas, and batch replacing the corresponding parameters in the configuration files of each of the replicas of each module according to the customized parameter list of each of the replicas, includes:

[0029] Execute the currently executable job flow and send the deployment execution agent to the server to be deployed;

[0030] The deployment steps are executed sequentially according to the deployment step file in the deployment execution agent;

[0031] Based on the customized parameter list of each replica, the corresponding parameters in the configuration files of each replica of each module are replaced in batches.

[0032] A second aspect of this application provides an apparatus for processing application version parameters, comprising:

[0033] The first acquisition unit is used to acquire the user-imported software package to be processed;

[0034] The parsing unit is used to parse the software package to be processed and obtain the customizable parameters corresponding to each module in the software package to be processed.

[0035] The task creation unit is used to respond to the user's task creation operation and create a deployment task for the software package to be processed;

[0036] The calculation unit is used to calculate each of the parameters to be customized using a pre-set calculation method to obtain multiple calculated parameter values;

[0037] The distribution unit is used to distribute each of the calculated parameter values ​​to the corresponding replicas according to the type of each calculated parameter value, so as to obtain a customized parameter list for each replica.

[0038] The generation unit is used to generate a currently executable job flow based on the installation method of each of the modules;

[0039] The deployment unit is used to execute the currently executable job flow to deploy each of the replicas, and to batch replace the corresponding parameters in the configuration files of each of the replicas of each module according to the customized parameter list of each of the replicas.

[0040] Optionally, in the above-described application version parameter processing apparatus, the calculation unit includes:

[0041] The first query unit is used to query, for each of the parameters to be customized, whether the calculation method type corresponding to the parameter to be customized is template-first based on the keyword of the parameter to be customized;

[0042] The second query unit is used to query whether the calculation parameter value corresponding to the parameter to be customized exists in the parameter configuration center when the calculation method type corresponding to the parameter to be customized is template priority.

[0043] The return unit is used to return the calculated parameter value corresponding to the parameter to be customized when the calculated parameter value corresponding to the parameter to be customized exists in the parameter configuration center.

[0044] The third query unit is used to query the SQL statement and method input parameters associated with the calculation method identifier corresponding to the parameter to be customized when the query finds that the calculation method type corresponding to the parameter to be customized is not template priority, or when the query finds that the calculation parameter value corresponding to the parameter to be customized does not exist in the parameter configuration center.

[0045] The calculation subunit is used to calculate the calculation parameter value corresponding to the parameter to be customized based on the SQL statement and the method parameters.

[0046] Optionally, in the above-mentioned processing and transposition of application version parameters, the distribution unit includes:

[0047] The first distribution unit is configured to distribute the calculated parameter value to each copy of each module for each calculated parameter value. If the calculated parameter value is a product-level parameter, the calculated parameter value is distributed to each copy of the module to obtain a customized parameter list for each copy.

[0048] The second distribution unit is used to distribute the calculation parameter value to each copy of the module to which it belongs when the calculation parameter value is a module-level parameter, so as to obtain a customized parameter list for each copy.

[0049] The third distribution unit is used to distribute the calculation parameter value to the corresponding replica when the calculation parameter value is a replica-level parameter, thereby obtaining a list of customized parameters for the replica.

[0050] Optionally, in the above-mentioned processing and transposition of application version parameters, the generation unit includes:

[0051] The second acquisition unit is used to acquire the installation method of each module according to the type of the module;

[0052] The first replacement unit is used to replace the parameters of each command module in the installation method of the module to obtain the current executable job flow corresponding to the module.

[0053] Optionally, in the above-mentioned processing and transposition of application version parameters, the deployment unit includes:

[0054] The first execution unit is used to execute the currently executable job flow and send the deployment execution agent to the server to be deployed;

[0055] The second execution unit is used to execute the deployment steps sequentially according to the deployment step file in the deployment execution agent;

[0056] The second replacement unit is used to replace the corresponding parameters in the configuration files of each copy of each module in batches according to the customized parameter list of each copy.

[0057] A third aspect of this application provides an electronic device, comprising:

[0058] Memory and processor;

[0059] The memory is used to store programs;

[0060] The processor is used to execute the program, which, when executed, is specifically used to implement the application version parameter processing method as described in any of the above.

[0061] A fourth aspect of this application provides a computer storage medium for storing a computer program, which, when executed, implements the application version parameter processing method as described in any of the preceding claims.

[0062] This application provides a method for processing application version parameters. It obtains a user-imported software package to be processed, parses the package to obtain the customization parameters corresponding to each module within it, and then responds to the user's task creation operation to create a deployment task for the software package. Using a pre-set calculation method, it calculates each customization parameter to obtain multiple calculated parameter values. Then, based on the type of each calculated parameter value, it distributes them to the corresponding replicas, obtaining a customization parameter list for each replica. Next, based on the installation method of each module, it generates and executes a currently executable job flow to deploy each replica. Finally, based on the customization parameter list of each replica, it batch replaces the corresponding parameters in the configuration files of each replica of each module, thereby achieving automatic deployment of the software package and automatic data customization, effectively improving efficiency. Attached Figure Description

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

[0064] Figure 1 This application provides an architecture diagram of an application deployment system.

[0065] Figure 2 A flowchart illustrating a method for processing application version parameters provided in this application embodiment;

[0066] Figure 3 A flowchart illustrating a method for calculating customized parameters provided in this application embodiment;

[0067] Figure 4 A flowchart illustrating a method for generating a currently executable job flow, provided in an embodiment of this application;

[0068] Figure 5 A flowchart illustrating a method for deploying copies, as provided in an embodiment of this application;

[0069] Figure 6 A schematic diagram of the architecture of an application version parameter processing device provided in an embodiment of this application;

[0070] Figure 7 This is a schematic diagram of the architecture of an electronic device provided in an embodiment of this application. Detailed Implementation

[0071] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and 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.

[0072] In this application, 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 terms "comprising," "including," or any other variations thereof are 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 limitation, 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 said element.

[0073] This application provides a method for processing application version parameters to solve the problem of relatively low efficiency in the prior art.

[0074] Optionally, to implement the application version parameter processing method provided in this application embodiment, this application embodiment provides an application deployment system, such as... Figure 1 As shown, it includes:

[0075] Application layer, basic service layer, and storage layer.

[0076] The data storage layer can include MySQL and FTP. MySQL is mainly used to store configuration parameters, deployment task information, and metadata. FTP mainly stores software packages and the scripts for each command template.

[0077] The basic service layer mainly includes a software package parsing module, a parameter configuration center module, a parameter calculation engine, a job flow orchestration engine, and a scheduling engine.

[0078] The software parsing module is mainly used to automatically parse deployment module information and parameter information from user-imported software packages.

[0079] The parameter configuration center module is primarily used to manage all deployment parameters for all products, providing users with CRUD (Create, Read, Update, Delete) functionality for parameters. This module allows for hierarchical parameter management, categorizing parameters into three types based on their scope: product-level parameters, module-level parameters, and copy-level parameters.

[0080] The parameter calculation engine is mainly used to calculate the parameter value for each parameter to be customized and store it in the deployment task management module, providing parameter information for subsequent generation of deployment job flow and deployment execution.

[0081] The job flow orchestration engine is mainly used to obtain the installation method of the module based on the type of the deployed module, obtain the deployment command template for each installation method from the command management module, and replace the parameters in the command template with the parameter values ​​of this deployment to form an executable job flow.

[0082] The scheduling engine is primarily responsible for task scheduling, i.e., the actual execution of deployments. Specifically, it can adopt an event-driven pattern. When deployment begins, a deployment agent is dynamically sent to the target server. Based on the deployment step XML file within the agent, the deployment steps are executed sequentially, while simultaneously replacing parameter file values. At the same time, execution logs are synchronously updated to the web interface.

[0083] The application layer mainly includes a server management module, a software package management module, a deployment task management module, a command management module, and a deployment execution visualization module.

[0084] The server management module, package management module, deployment task management module, and command management module are all used to manage the relevant data and provide the managed information for deployment tasks.

[0085] The deployment and execution visualization module is mainly used to visualize information during the deployment process, allowing users to confirm information and understand the deployment progress in a timely manner.

[0086] Based on the application deployment system provided above, this application embodiment provides a method for processing application version parameters, such as... Figure 2 As shown, it includes:

[0087] S201. Obtain the user-imported software package to be processed.

[0088] Specifically, users perform work stamping and package assembly operations according to preset package assembly rules to obtain the software package to be processed, and then import it into the system.

[0089] S202. Parse the software package to be processed to obtain the customizable parameters corresponding to each module in the software package.

[0090] It should be noted that a module is the smallest independent deployment unit within a software package.

[0091] Optionally, the parameters included within the module can be parsed and recorded in the package parameter information table (ez_soft_para). These parameters may include the module, filename, file path, parameter type, parameter key, and initial parameter value. Furthermore, information related to the module itself can be parsed and recorded in the package module information table (ez_soft_module). This information may include the package, module type, module name, and module start / stop commands. This information is used to determine which parameters to calculate and which modules to generate deployment job flows for.

[0092] S203. In response to the user's task creation operation, create a deployment task for the pending software package.

[0093] To facilitate the automatic execution of subsequent deployment tasks, users need to create deployment tasks.

[0094] Optionally, when creating a deployment task, users can select the task name, the software package to be processed, the deployment environment, and the deployment mode.

[0095] S204. Using a pre-set calculation method, calculate each parameter to be customized to obtain multiple calculated parameter values.

[0096] Specifically, after a deployment task is created, the automated deployment tool performs parameter calculations to provide data support for subsequent deployments. Specifically, it can calculate customized parameters based on pre-set calculation rules.

[0097] Optionally, in another embodiment of this application, one specific implementation of step S204 is as follows: Figure 3 As shown, it includes:

[0098] S301. For each parameter to be customized, query whether the calculation method type corresponding to the parameter to be customized is template-first based on the keyword of the parameter to be customized.

[0099] It should be noted that in this application, the calculation method types are divided into template-first and calculation-first. Parameters for template-first calculation can be directly obtained from the parameter configuration center. Parameters for calculation-first calculation are related to the deployment environment and therefore need to be dynamically generated based on the deployment requirements set in this deployment task.

[0100] Therefore, if the query finds that the calculation method type corresponding to the parameter to be customized is template priority, then step S302 is executed. If the query finds that the calculation method type corresponding to the parameter to be customized is not template priority, that is, the calculation method type corresponding to the parameter to be customized is calculation priority, then step S304 is executed.

[0101] S302. Check if the calculated parameter value corresponding to the parameter to be customized exists in the parameter configuration center.

[0102] If the parameter configuration center contains a calculated parameter value corresponding to the parameter to be customized, then step S303 is executed. If the parameter configuration center does not contain a calculated parameter value corresponding to the parameter to be customized, then it means that it still needs to be calculated, so step S304 is executed.

[0103] S303. Returns the calculated parameter value corresponding to the parameter to be customized.

[0104] S304. Query the SQL statement and method input parameters associated with the calculation method identifier corresponding to the parameter to be customized.

[0105] Specifically, corresponding calculation method identifiers can be set in advance based on the type of each parameter to be customized. Furthermore, the SQL statements and input parameters for each calculation method identifier are pre-maintained.

[0106] Therefore, the SQL statement associated with the calculation method identifier corresponding to the parameter to be customized and the method input parameters can be retrieved, and then step S305 can be executed.

[0107] S305. Based on the SQL statement and method parameters, calculate the value of the calculated parameter corresponding to the parameter to be customized.

[0108] Optionally, to ensure that the calculated parameter values ​​meet the user's requirements, in another embodiment of this application, after obtaining the calculated parameter values, the calculated parameter values ​​can be fed back to the user for confirmation. After the user confirms that the calculated parameter values ​​are correct, step S205 is then executed.

[0109] S205. Distribute each calculated parameter value to the corresponding replica according to the type of each calculated parameter value, and obtain the customized parameter list for each replica.

[0110] It should be noted that each module can be deployed on multiple servers, and the deployment of a module on one server is called a replica.

[0111] Therefore, by querying the mapping relationship between modules and deployment servers, the replicas of each module can be determined. Then, based on the type of each calculation parameter value, the calculation parameter values ​​can be distributed to the corresponding replicas to obtain the customized parameter list for each replica.

[0112] Optionally, in the embodiments of this application, the calculated parameter values ​​are divided into three types: product-level parameters, module-level parameters, and copy-level parameters.

[0113] Among them, the scope of product-level parameters is the entire parameter, that is, each copy of each module under the product shares the same parameter value.

[0114] The scope of a module-level parameter is a specific module within a product. This means that different modules within a product can have different parameter values, while copies within the same module share the relevant parameter values.

[0115] The scope of a replica-level parameter is one replica within a module of a product; that is, each IP address deployed in the module can have a different parameter value.

[0116] Therefore, one specific implementation of step S205 includes:

[0117] For each calculated parameter value, if the calculated parameter value is a product-level parameter, the calculated parameter value is distributed to each copy of each module to obtain a customized parameter list for each copy.

[0118] If the calculated parameter value is a module-level parameter, then the calculated parameter value is distributed to each copy of the module to which it belongs, resulting in a list of customized parameters for each copy.

[0119] If the calculated parameter value is a replica-level parameter, then the calculated parameter value is distributed to the corresponding replica, resulting in a list of customized parameters for the replica.

[0120] Optionally, after distributing the calculated parameter values ​​to the replicas, the information of each replica can also be displayed to the user for confirmation on the front end.

[0121] S206. Generate the current executable job flow based on the installation method of each module.

[0122] Specifically, such as Figure 4 As shown, one specific implementation of step S206 includes:

[0123] S401. For each module, obtain the module installation method according to the module type.

[0124] S402. Replace the parameters of each command module in the installation method of the replacement module to obtain the current executable job flow corresponding to the module.

[0125] Similarly, the generated executable job flow can be displayed to the user for confirmation.

[0126] S207. Execute the currently executable job flow to deploy each replica, and batch replace the corresponding parameters in the configuration files of each replica of each module according to the customized parameter list of each replica.

[0127] Alternatively, in another embodiment of this application, one specific manner of step S207 is as follows: Figure 5 As shown, the package includes the following steps:

[0128] S501. Execute the currently executable job flow and send the deployment execution agent to the server to be deployed.

[0129] Optionally, the issued deployment execution agent may include push agent execution code, deployment workflow, customized parameter list, and agent process startup.

[0130] S502. Execute the deployment steps sequentially according to the deployment step file in the deployment execution agent.

[0131] S503. Based on the customized parameter list of each copy, batch replace the corresponding parameters in the configuration files of each copy of each module.

[0132] Specifically, based on the parameter file information to be customized and the list of customized parameters, the values ​​of the corresponding configuration files on each copy of each module are replaced in batches, thereby achieving parameter customization.

[0133] This application provides a method for processing application version parameters. It obtains a user-imported software package to be processed, parses the package to obtain the customization parameters corresponding to each module within it, and then responds to the user's task creation operation to create a deployment task for the software package. Using a pre-set calculation method, it calculates each customization parameter to obtain multiple calculated parameter values. Then, based on the type of each calculated parameter value, it distributes them to the corresponding replicas, obtaining a customization parameter list for each replica. Next, based on the installation method of each module, it generates and executes a currently executable job flow to deploy each replica. Finally, based on the customization parameter list of each replica, it batch replaces the corresponding parameters in the configuration files of each replica of each module, thereby achieving automatic deployment of the software package and automatic data customization, effectively improving efficiency.

[0134] Another embodiment of this application provides an application version parameter processing apparatus, such as... Figure 6 As shown, it includes:

[0135] The first acquisition unit 601 is used to acquire the software package to be processed imported by the user.

[0136] The parsing unit 602 is used to parse the software package to be processed and obtain the customizable parameters corresponding to each module in the software package.

[0137] The task creation unit 603 is used to respond to the user's task creation operation and create a deployment task for the software package to be processed.

[0138] The calculation unit 604 is used to calculate each custom parameter using a pre-set calculation method to obtain multiple calculated parameter values.

[0139] The distribution unit 605 is used to distribute each calculation parameter value to the corresponding replica according to the type of each calculation parameter value, so as to obtain the customized parameter list of each replica.

[0140] The generation unit 606 is used to generate the current executable job flow according to the installation method of each module.

[0141] Deployment unit 607 is used to execute the currently executable job flow to deploy each replica, and to batch replace the corresponding parameters in the configuration files of each replica of each module according to the customized parameter list of each replica.

[0142] Optionally, in another embodiment of the application version parameter processing apparatus provided in this application, the calculation unit includes:

[0143] The first query unit is used to query, for each parameter to be customized, whether the calculation method type corresponding to the parameter to be customized is template-first, based on the keyword of the parameter to be customized.

[0144] The second query unit is used to query whether the calculation parameter value corresponding to the parameter to be customized exists in the parameter configuration center when the calculation method type corresponding to the parameter to be customized is template priority.

[0145] The return unit is used to return the calculated parameter value corresponding to the parameter to be customized when the calculated parameter value corresponding to the parameter to be customized exists in the parameter configuration center.

[0146] The third query unit is used to query the SQL statement associated with the calculation method identifier corresponding to the parameter to be customized and the method input parameters when the query finds that the calculation method type corresponding to the parameter to be customized is not template priority, or when the query finds that the calculation parameter value corresponding to the parameter to be customized does not exist in the parameter configuration center.

[0147] The calculation subunit is used to calculate the calculation parameter value corresponding to the parameter to be customized based on the SQL statement and method parameters.

[0148] Optionally, in another embodiment of the application version parameter processing apparatus provided in this application, the distribution unit includes:

[0149] The first distribution unit is used to distribute the calculated parameter value to each copy of each module if the calculated parameter value is a product-level parameter, thereby obtaining a customized parameter list for each copy.

[0150] The second distribution unit is used to distribute the calculated parameter value to each copy of the module when the calculated parameter value is a module-level parameter, so as to obtain a list of customized parameters for each copy.

[0151] The third distribution unit is used to distribute the calculated parameter value to the corresponding replica when the calculated parameter value is a replica-level parameter, thereby obtaining a list of customized parameters for the replica.

[0152] Optionally, in another embodiment of the application version parameter processing apparatus provided in this application, the generation unit includes:

[0153] The second acquisition unit is used to acquire the installation method of each module according to the module type.

[0154] The first replacement unit is used to replace the parameters of each command module in the module installation method to obtain the current executable job flow corresponding to the module.

[0155] Optionally, in another embodiment of the application version parameter processing apparatus provided in this application, the deployment unit includes:

[0156] The first execution unit is used to execute the currently executable job flow and distribute the deployment execution agent to the server to be deployed.

[0157] The second execution unit is used to execute the deployment steps sequentially according to the deployment step file in the deployment execution agent.

[0158] The second replacement unit is used to batch replace the corresponding parameters in the configuration files of each copy of each module according to the customized parameter list of each copy.

[0159] It should be noted that the various units provided in the above embodiments of this application can be... Figure 1 The components of each module in the system are shown, and the specific working process of each unit can be referred to the corresponding steps in the above method embodiments, which will not be repeated here.

[0160] Another embodiment of this application provides an electronic device, such as... Figure 7 As shown, it includes:

[0161] Memory 701 and processor 702.

[0162] The memory 701 is used to store the program.

[0163] The processor 702 is used to execute the program stored in the memory 701, and when the program is executed, it is specifically used to implement the processing method of application version parameters as provided in any of the above embodiments.

[0164] Another embodiment of this application provides a computer storage medium for storing a computer program, which, when executed, implements the application version parameter processing method provided in any of the above embodiments.

[0165] Computer storage media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. 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), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0166] It should be noted that the application version parameter processing method, apparatus, electronic device, and storage medium provided by this invention can be used in the distributed computing or financial fields. The above are merely examples and do not limit the application fields of the application version parameter processing method, apparatus, electronic device, and storage medium provided by this invention.

[0167] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0168] The above description of the disclosed embodiments enables those skilled in the art to make or use 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 the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for processing application version parameters, characterized in that, include: Retrieve user-imported packages to be processed; The software package to be processed is parsed to obtain the customization parameters corresponding to each module in the software package; In response to the user's task creation operation, a deployment task for the pending software package is created; Using a pre-set calculation method, each of the parameters to be customized is calculated to obtain multiple calculated parameter values; The step of using a pre-set calculation method to calculate each of the parameters to be customized, resulting in multiple calculated parameter values, including: For each of the parameters to be customized, based on the keyword of the parameter to be customized, query whether the calculation method type corresponding to the parameter to be customized is template-first; If the query finds that the calculation method type corresponding to the parameter to be customized is template priority, then query whether the calculation parameter value corresponding to the parameter to be customized exists in the parameter configuration center; If the calculated parameter value corresponding to the parameter to be customized exists in the parameter configuration center, then the calculated parameter value corresponding to the parameter to be customized is returned. If the query finds that the calculation method type corresponding to the parameter to be customized is not template priority, or if the query finds that the calculation parameter value corresponding to the parameter to be customized does not exist in the parameter configuration center, then the SQL statement associated with the calculation method identifier corresponding to the parameter to be customized and the method input parameters are retrieved. Based on the SQL statement and the method input parameters, the calculated parameter value corresponding to the parameter to be customized is obtained; Based on the type of each calculated parameter value, each calculated parameter value is distributed to the corresponding replica to obtain a customized parameter list for each replica; Based on the installation method of each module, generate the current executable job flow; The currently executable job flow is executed to deploy each of the replicas, and the corresponding parameters in the configuration files of each of the replicas of each module are replaced in batches according to the customized parameter list of each of the replicas.

2. The method according to claim 1, characterized in that, The step of distributing each calculated parameter value to a corresponding replica according to the type of each calculated parameter value, to obtain a customized parameter list for each replica, includes: For each of the calculated parameter values, if the calculated parameter value is a product-level parameter, then the calculated parameter value is distributed to each of the replicas of each module to obtain a customized parameter list for each replica. If the calculated parameter value is a module-level parameter, then the calculated parameter value is distributed to each copy of the module to which it belongs, so as to obtain a customized parameter list for each copy. If the calculated parameter value is a replica-level parameter, then the calculated parameter value is distributed to the corresponding replica to obtain a list of customized parameters for the replica.

3. The method according to claim 1, characterized in that, The step of generating the current executable job flow according to the installation method of each module includes: For each module, obtain the installation method for that module based on its type; Replace the parameters of each command module in the module installation method to obtain the current executable job flow corresponding to the module.

4. The method according to claim 1, characterized in that, The execution of the currently executable job flow to deploy each of the replicas, and the batch replacement of corresponding parameters in the configuration files of each of the replicas of each module according to the customized parameter list of each of the replicas, includes: Execute the currently executable job flow and send the deployment execution agent to the server to be deployed; The deployment steps are executed sequentially according to the deployment step file in the deployment execution agent; Based on the customized parameter list of each replica, the corresponding parameters in the configuration files of each replica of each module are replaced in batches.

5. An application version parameter processing device, characterized in that, include: The first acquisition unit is used to acquire the user-imported software package to be processed; The parsing unit is used to parse the software package to be processed and obtain the customizable parameters corresponding to each module in the software package to be processed. The task creation unit is used to respond to the user's task creation operation and create a deployment task for the software package to be processed; The calculation unit is used to calculate each of the parameters to be customized using a pre-set calculation method to obtain multiple calculated parameter values; The computing unit includes: The first query unit is used to query, for each of the parameters to be customized, whether the calculation method type corresponding to the parameter to be customized is template-first based on the keyword of the parameter to be customized; The second query unit is used to query whether the calculation parameter value corresponding to the parameter to be customized exists in the parameter configuration center when the calculation method type corresponding to the parameter to be customized is template priority. The return unit is used to return the calculated parameter value corresponding to the parameter to be customized when the calculated parameter value corresponding to the parameter to be customized exists in the parameter configuration center. The third query unit is used to query the SQL statement and method input parameters associated with the calculation method identifier corresponding to the parameter to be customized when the query finds that the calculation method type corresponding to the parameter to be customized is not template priority, or when the query finds that the calculation parameter value corresponding to the parameter to be customized does not exist in the parameter configuration center. The calculation subunit is used to calculate the calculation parameter value corresponding to the parameter to be customized based on the SQL statement and the method input parameters; The distribution unit is used to distribute each of the calculated parameter values ​​to the corresponding replicas according to the type of each calculated parameter value, so as to obtain a customized parameter list for each replica. The generation unit is used to generate a currently executable job flow based on the installation method of each of the modules; The deployment unit is used to execute the currently executable job flow to deploy each of the replicas, and to batch replace the corresponding parameters in the configuration files of each of the replicas of each module according to the customized parameter list of each of the replicas.

6. The apparatus according to claim 5, characterized in that, The distribution unit includes: The first distribution unit is configured to distribute the calculated parameter value to each copy of each module for each calculated parameter value. If the calculated parameter value is a product-level parameter, the calculated parameter value is distributed to each copy of the module to obtain a customized parameter list for each copy. The second distribution unit is used to distribute the calculation parameter value to each copy of the module to which it belongs when the calculation parameter value is a module-level parameter, so as to obtain a customized parameter list for each copy. The third distribution unit is used to distribute the calculation parameter value to the corresponding replica when the calculation parameter value is a replica-level parameter, thereby obtaining a list of customized parameters for the replica.

7. An electronic device, characterized in that, include: Memory and processor; The memory is used to store programs; The processor is used to execute the program, which, when executed, is specifically used to implement the application version parameter processing method as described in any one of claims 1 to 4.

8. A computer storage medium, characterized in that, Used to store a computer program, which, when executed, implements the method for processing application version parameters as described in any one of claims 1 to 4.

Images