Configuration Management Method and Related Devices for Micro-Applications

Abstract

The present application provides a method for configuring and managing micro-applications and related devices; the method includes: creating a metadata baseline during the development stage of the micro-application, and in the metadata baseline, recording all current parameters in the micro-application as a parameter snapshot; when any parameter is modified, adding at least one parameter snapshot to the current metadata baseline; during the production stage, configuring the parameters of the micro-application by using the parameter snapshots determined from the metadata baseline; creating a production configuration baseline corresponding to the production stage, and recording a production parameter value snapshot in the production configuration baseline, where the production parameter value snapshot includes the production parameter values of all parameters in the production stage; during the production stage of the micro-application, when any parameter is modified, adding at least one parameter snapshot to the current metadata baseline, and when any production parameter value is modified, adding at least one production parameter value snapshot to the production configuration baseline. This method uses the corresponding baseline as the specification for configuration management, improving the efficiency of configuration management.

Description

Technical Field

[0001] Embodiments of the present application relate to the technical field, and in particular, to a method for configuring and managing micro-applications and related devices. Background Art

[0002] In the related methods for configuring micro-applications, since micro-applications need to go through different environments deployed in different stages, therefore, in each environment, it is necessary to reconfigure the configuration items of the micro-applications, making the process of configuring the configuration items very cumbersome and inefficient. And sometimes the relevant parameters that need to be configured for the configuration items, as well as the parameter values configured for each parameter, will also be different, making the configuration process of the configuration items extremely prone to configuration errors.

[0003] Based on this, there is a need for a method that can quickly configure the configuration items of micro-applications in different environments, and at the same time improve efficiency, and this solution also needs to be able to effectively reduce the error rate during the configuration process. Summary of the Invention

[0004] In view of this, the purpose of the present application is to propose a method for configuring and managing micro-applications and related devices.

[0005] Based on the above purpose, the present application provides a method for configuring and managing micro-applications, including:

[0006] Create a metadata baseline during the development stage of the micro-application. In the metadata baseline, record all current parameters in the micro-application as parameter snapshots; in response to determining that any of the parameters is modified, add at least one parameter snapshot to the current metadata baseline;

[0007] During the production stage of the micro-application, configure the parameters of the micro-application using the parameter snapshots determined from the current metadata baseline; create a production configuration baseline corresponding to the production stage, and record a production parameter value snapshot in the production configuration baseline, where the production parameter value snapshot includes the production parameter values of all the parameters in the production stage;

[0008] During the production stage of the micro-application, in response to determining that any of the parameters is modified, add at least one parameter snapshot to the current metadata baseline, and in response to determining that any of the production parameter values is modified, add at least one production parameter value snapshot to the production configuration baseline.

[0009] Further, in any stage of the micro-application, it further includes:

[0010] In response to determining that the parameters currently configured for the micro-application are incorrect, select other parameter snapshots in the metadata baseline except the current parameter snapshot, and configure new parameters for the micro-application using the selected parameter snapshots;

[0011] In response to an error in the production parameter value currently configured for the parameter, select other production parameter value snapshots in the production configuration baseline except the current parameter value snapshot, and fill in the new production parameter value for the parameter using the selected production parameter value snapshot.

[0012] Further, after creating the metadata baseline in the development stage of the micro - application, it further includes:

[0013] In each environment deployed in the development stage, select 1 parameter snapshot from the metadata baseline, and configure the parameters for the micro - application using the selected parameter snapshot;

[0014] In each environment in the development stage, establish an environment configuration baseline for the micro - application, and record the parameter values of the parameters in the corresponding environment in the environment configuration baseline.

[0015] Further, the recording the parameter values of the parameters in the corresponding environment in the environment configuration baseline includes:

[0016] In each environment in the development stage, fill in the environment parameter values corresponding to the environment for all parameters;

[0017] In the environment configuration baseline, record the environment parameter values of all current parameters in the environment as 1 environment parameter value snapshot corresponding to the environment;

[0018] In response to determining that any of the environment parameter values is modified, record the modified all environment parameter values in the environment configuration baseline as 1 new environment parameter value snapshot corresponding to the environment.

[0019] Further, in any stage of the micro - application, the adding at least one parameter snapshot in the current metadata baseline in response to determining that any parameter is modified includes:

[0020] In response to determining that any parameter is modified, record the modified all parameters in the current metadata baseline as 1 new parameter snapshot.

[0021] Further, after the micro - application completes the development stage and before entering the production stage, it further includes:

[0022] Save the metadata baseline recording all the parameter snapshots to the pre - production library in the delivery stage;

[0023] The configuring the parameters for the micro - application using the parameter snapshot determined from the current metadata baseline includes:

[0024] Find the metadata baseline from the pre-production library;

[0025] Select a predetermined snapshot of the parameters from the metadata baseline and configure it.

[0026] Further, in response to determining that any of the production parameter values is modified, add at least one snapshot of the production parameter values to the production configuration baseline, including:

[0027] In response to determining that any of the production parameter values is modified, record all the modified production parameter values as 1 new snapshot of the production parameter values in the production configuration baseline.

[0028] Based on the same inventive concept, the present application also provides a configuration management device for a micro-application, including:

[0029] A development module, configured to create a metadata baseline during the development stage of the micro-application, and record all current parameters in the micro-application as parameter snapshots in the metadata baseline; in response to determining that any of the parameters is modified, add at least one parameter snapshot to the current metadata baseline;

[0030] An initialization production module, configured to, during the production stage of the micro-application, configure the parameters of the micro-application by using the parameter snapshots determined from the current metadata baseline; create a production configuration baseline corresponding to the production stage, and record production parameter value snapshots in the production configuration baseline, where the production parameter value snapshots include the production parameter values of all the parameters in the production stage;

[0031] An update production module, configured to, during the production stage of the micro-application, in response to determining that any of the parameters is modified, add at least one parameter snapshot to the current metadata baseline, and in response to determining that any of the production parameter values is modified, add at least one production parameter value snapshot to the production configuration baseline.

[0032] Based on the same inventive concept, the present application also provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where when the processor executes the program, it implements the configuration management method of the micro-application as described in any one of the above.

[0033] Based on the same inventive concept, the present application also provides a non-transitory computer-readable storage medium, where the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to cause the computer to execute the configuration management method of the micro-application as described above.

[0034] It can be seen that in the rollback operation and the configuration item configuration operations in each environment, the Meta baseline and the corresponding environment configuration baseline can be used as the specifications for configuration management in each stage of the configuration life cycle, and this specification is used to uniformly standardize the configuration items of the micro application.

[0035] It can be seen that the configuration management method for the micro application in the embodiments of the present application, based on the Meta baseline and the environment configuration baseline set for the configuration items, comprehensively considers the different configuration life cycles of the relevant configurations, that is, the different relevant configurations of each configuration item in each environment deployed in each stage, to update the Meta baseline and the corresponding environment configuration baseline, so that any modification of any configuration item in any environment can be recorded in the Meta baseline or the corresponding environment configuration baseline, thereby realizing the use of the Meta baseline and the environment configuration baseline as the specifications for configuration management between each environment. That is to say, in the process of change, modification, delivery, and rollback of the configuration items, this specification can be used to perform relevant operations on the configuration items, thereby improving the accuracy and efficiency of configuration item management. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the present application or related technologies, the following will briefly introduce the drawings required for use in the description of the embodiments or related technologies. Obviously, the drawings in the following description are only the embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0037] Figure 1a It is a flowchart of the configuration management method for the micro application in the embodiments of the present application;

[0038] Figure 1b It is a schematic diagram of the architecture of the configuration management method for the micro application in the embodiments of the present application;

[0039] Figure 2 It is a schematic diagram of the configuration management device for the micro application in the embodiments of the present application;

[0040] Figure 3 It is a schematic diagram of the structure of the electronic device in the embodiments of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0041] To make the objectives, technical solutions, and advantages of the present application clearer and more understandable, the following further elaborates on the present application in detail with reference to specific embodiments and the accompanying drawings.

[0042] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should have the ordinary meanings understood by those with ordinary skills in the field to which the present application belongs. The "first", "second" and similar terms used in the embodiments of the present application do not indicate any order, quantity or importance, but are only used to distinguish different components. Words such as "including" or "comprising" mean that the elements or objects appearing before this word cover the elements or objects listed after this word and their equivalents, without excluding other elements or objects.

[0043] As described in the background art section, the related configuration management methods for micro-applications are still difficult to meet the needs in actual production.

[0044] The applicant found in the process of implementing the present application that the main problems existing in the related configuration management methods for micro-applications are as follows: in the development stage and production stage of micro-applications, it is necessary to perform multiple configurations of parameters and configuration of parameter values for configuration items.

[0045] Specifically, different environments deployed in each stage can be regarded as the configuration life cycle of the micro-application configuration items. That is to say, not only in different stages, but also in different environments in the same stage, corresponding reconfigurations need to be carried out.

[0046] Among them, it includes the reconfiguration of each parameter of the configuration item, and the reconfiguration of the parameter values of each parameter in different environments.

[0047] The applicant also found in the research that the related configurations of configuration items are very complicated. Especially after the parameters or parameter values in the historical configurations are modified, it is very easy to miss individual configuration items or make configuration errors. And when configuration errors occur in related configuration items, it is often difficult to troubleshoot, bringing great pressure to production.

[0048] The applicant further found in the research that different baselines can be set for the parameters and parameter values of the configuration item respectively. By recording the configuration of the configuration item in the form of a snapshot, the historical modifications of the configuration item can be saved, and the saved records can also be used as a specification and standard when configuring the configuration item.

[0049] It can be understood that this method can be executed by any device, equipment, platform, or device cluster with computing and processing capabilities.

[0050] Hereinafter, through specific embodiments, the technical method of the present application will be described in detail.

[0051] In the embodiments of the present application, a micro - application needs to go through a development stage and a production stage. Specifically, the micro - application will be developed in the R & D environment during the development stage. The developed micro - application will be tested in the test environment during the development stage. The tested micro - application will enter the production environment during the production stage. Therefore, in this embodiment, the configuration management method for the micro - application will be described in detail based on the above - mentioned different stages and different environments in each stage.

[0052] Reference Figure 1a , the configuration management method for the micro - application in an embodiment of the present application includes the following steps:

[0053] Step S1a - 01: Create a metadata baseline during the development stage of the micro - application. In the metadata baseline, record all current parameters in the micro - application as parameter snapshots. In response to determining that any of the parameters is modified, add at least one parameter snapshot to the current metadata baseline.

[0054] In the embodiments of the present application, first, it is necessary to determine the micro - application for which configuration management is to be performed.

[0055] Normally, in an application system, there are often multiple micro - applications, and each of them needs to be configured and managed separately.

[0056] In some embodiments, since the version of the micro - application will be continuously upgraded or modified, a micro - application often has multiple application versions. For a micro - application with multiple application versions, each application version of the micro - application should be regarded as a separate micro - application, and each application version should be configured and managed separately. If the micro - application does not have multiple application versions, it can be directly configured and managed separately for each micro - application.

[0057] In this embodiment, Figure 1b the shown architecture is taken as a specific example.

[0058] Among them, as Figure 1b shown, in an application system A, there are multiple micro - applications: micro - application A, micro - application B, and micro - application C. Each micro - application can have multiple application versions. For example, the application versions of micro - application A include: application version 1.0, application version 2.0, and application version 3.0. In this embodiment, the application version 3.0 of micro - application A is determined as the micro - application for which configuration management is to be performed.

[0059] In the R & D environment, based on the determined specific micro - application, the configuration center in the micro - architecture initializes the metadata baseline and the environment configuration baseline for the micro - application.

[0060] Specifically, create an empty Meta baseline (metadata baseline) and an empty environment configuration baseline. Since the micro-application is in the R & D environment at this time, the environment configuration baseline can be called the R & D configuration baseline.

[0061] Furthermore, determine all the configuration items of the micro-application in the R & D environment at this time; among them, each configuration item includes: a currently configured Key (parameter), and the Value (parameter value) configured for this parameter in the R & D environment.

[0062] Furthermore, record the Keys of the full set of configuration items currently configured by the micro-application in the form of a snapshot to obtain a Key snapshot (parameter snapshot), label the key snapshot with a custom version number, and record it in the Meta baseline.

[0063] In Figure 1b In a specific example, snapshot-record the Keys of the full set of configuration items in application version 3.0 to obtain the Key snapshot of the full set of configuration items regarding Keys in the current application version 3.0, and name it MetaKey1.0 to indicate that the snapshot of this Key is version 1.0.

[0064] It should be noted that if in the R & D environment, there is already a Meta baseline with a Key snapshot, it is also possible to directly configure the configuration items of the micro-application according to the Keys of each configuration item reflected in the Key snapshot according to the specific situation.

[0065] Furthermore, record the Values configured for the current full set of Keys of the micro-application in the R & D environment in the form of a snapshot to obtain a R & D Value snapshot (parameter value snapshot) corresponding to the current R & D environment, label the R & D Value snapshot with a custom version number, and record it in the environment configuration baseline.

[0066] In Figure 1b In a specific example, snapshot-record the Values configured for the full set of Keys in application version 3.0 at this time to obtain the R & D Value snapshot of the full set of Keys in the current R & D environment, save it to the R & D configuration baseline, and name it ConfigX1.0 to indicate that the R & D Value snapshot is version 1.0.

[0067] Furthermore, in the R & D environment in the development stage, if any configuration item of the micro-application is changed, or any operation is performed on the configuration item by the developer, the configuration center records the change of the configuration item as a snapshot with a new version number in the corresponding baseline.

[0068] Specifically, if the developer performs operations such as deletion, modification, or addition on the Key of the micro-application in the R & D environment, the configuration center will take a snapshot record of the Key of the full set of configuration items of the micro-application again, and obtain a Key snapshot with a new version number in the Meta baseline.

[0069] In Figure 1b In a specific example, in the R & D environment, if any Key of any configuration item in application version 3.0 is changed, after the change, the configuration center within the micro-architecture to which micro-application A belongs takes a snapshot record of the Key of the full set of configuration items of application version 3.0, obtains a new Key snapshot after the change, and names it MetaKey2.0 to indicate that the Key snapshot is version 2.0. At this time, there are two versions of Key snapshots, MetaKey1.0 and MetaKey2.0, in the Meta baseline.

[0070] Furthermore, if the developer performs operations such as deletion, modification, or addition on the Value of any Key in the R & D environment, the configuration center will take a snapshot record of the Value of the full set of Keys again, and obtain a R & D Value snapshot with a new version number in the R & D configuration baseline.

[0071] In Figure 1b In a specific example, if the Value of any Key in application version 3.0 is changed, the configuration center takes a snapshot of the Value of the current configuration of the full set of Keys, obtains a new R & D Value snapshot after the change, names it ConfigX2.0 and saves it to the R & D configuration baseline to indicate that the R & D Value snapshot is version 2.0. At this time, there are two versions of R & D Value snapshots, ConfigX1.0 and ConfigX2.0, in the R & D configuration baseline.

[0072] In this embodiment, after the micro-application is developed, it will enter the test environment from the R & D environment to perform relevant tests on the micro-application.

[0073] It should be noted that in this embodiment, the test environment can be multiple types of test environments such as a stress test environment.

[0074] After the micro-application enters the test environment, it will pull the Key snapshot with the corresponding version number from the Meta baseline, and use the Key reflected in the MetaKey snapshot to configure the configuration items for the micro-application in the test environment.

[0075] Among them, the Key snapshot pulled by the micro-application from the Meta baseline at this time can be the Key snapshot with the latest version number, or other Key snapshots that meet the configuration requirements according to specific circumstances.

[0076] In Figure 1b specific examples, after the application version 3.0 enters the test environment, it will pull the Key snapshot of the latest version number from the Meta baseline: MetaKey2.0.

[0077] Furthermore, the pulled Key snapshot MetaKey2.0 should be a full set that includes all the Keys of the configuration items in this micro-application. Therefore, the configuration items' Keys of the application version 3.0 in the test environment can be configured according to the Keys recorded in MetaKey2.0.

[0078] Furthermore, based on the micro-application with the Key configuration completed above, assign values to the Keys of each configuration item and establish a test configuration baseline for the corresponding test environment.

[0079] Specifically, determine the Value required for each Key of this micro-application in the test environment according to the specific situation, and assign each Value to the corresponding Key.

[0080] Furthermore, record the Values configured for the current full set of Keys of this micro-application in the test environment in the form of a snapshot, obtain a test Value snapshot corresponding to the current test environment, label the test Value snapshot with a custom version number, and record it in the environment configuration baseline.

[0081] In this embodiment, environment configuration baselines are established for all environments deployed in all stages such as the R & D environment, the test environment, and the following production environment, etc., to ensure that when modifying the Value of the Key, the respective environment configuration baselines can be directly used to avoid mutual interference caused by different Values of the Key among different environments.

[0082] In Figure 1b specific examples, take a snapshot record of the Values currently configured for the full set of Keys in the application version 3.0, obtain a test Value snapshot of the current full set of Keys in the test environment, name it ConfigY1.0, and save it to the test configuration baseline to indicate that this test Value snapshot is of version 1.0.

[0083] Furthermore, in the test environment during the development stage, if any configuration item of the micro-application is changed, or any operation is performed on the configuration item by the developer, the configuration center will record the change of the configuration item as a snapshot with a new version number in the corresponding baseline.

[0084] Specifically, if a developer performs operations such as deletion, modification, or addition on the Key of a micro-application in the test environment, the configuration center will take a snapshot record of the Key of the full set of configuration items of the micro-application again, and obtain a Key snapshot with a new version number in the Meta baseline.

[0085] In Figure 1b In a specific example, in the test environment, if any Key of any configuration item in application version 3.0 is changed, after the change, the configuration center within the micro-architecture to which micro-application A belongs takes a snapshot record of the Key of the full set of configuration items of application version 3.0, obtains a new Key snapshot after the change, and names it MetaKey3.0 to indicate that the Key snapshot is of version 3.0. At this time, there are three version Key snapshots, namely MetaKey1.0, MetaKey2.0, and MetaKey3.0, in the Meta baseline.

[0086] Furthermore, if a developer performs operations such as deletion, modification, or addition on the Value of any Key in the test environment, the configuration center will take a snapshot record of the Value of the full set of Keys again, and obtain a test Value snapshot with a new version number in the test configuration baseline.

[0087] In Figure 1b In a specific example, if the Value of any Key in application version 3.0 is changed, the configuration center takes a snapshot of the Value of the current configuration of the full set of Keys, obtains a new test Value snapshot after the change, names it ConfigY2.0, and saves it to the test configuration baseline to indicate that the test Value snapshot is of version 2.0. At this time, there are two version test Value snapshots, namely ConfigY1.0 and ConfigY2.0, in the test configuration baseline.

[0088] In this embodiment, as Figure 1b shown, after the micro-application completes testing, it will enter the delivery stage from the development stage. In the delivery stage, the relevant Meta baseline related to the micro-application will be delivered to the pre-production library in the micro-architecture.

[0089] Step S1a-02: In the production stage of the micro-application, configure parameters for the micro-application by using the parameter snapshots determined from the current metadata baseline; create a production configuration baseline corresponding to the production stage, and record a production parameter value snapshot in the production configuration baseline, where the production parameter value snapshot includes the production parameter values of all the parameters in the production stage.

[0090] In the embodiments of the present application, based on the above-delivered relevant Meta baseline, configuration management can be performed on the micro-application in the production stage.

[0091] It should be noted that multiple different environments can be deployed in the production stage of the micro - application. In this embodiment, only the deployed production environment is taken as a specific example to describe the configuration management method.

[0092] First, after the micro - application enters the production environment, find the Meta baseline corresponding to the micro - application from the pre - production library, pull the Key snapshot of the corresponding version number from the found Meta baseline, and configure the configuration items of the micro - application in the production environment using the Key reflected in the MetaKey snapshot.

[0093] Among them, the Key snapshot pulled by the micro - application from the Meta baseline at this time can be the Key snapshot of the latest version number, or other Key snapshots that meet the configuration requirements according to specific circumstances.

[0094] In Figure 1b In a specific example, after the application version 3.0 enters the production environment, it will pull the Key snapshot of the latest version number: MetaKey3.0 from the Meta baseline.

[0095] Furthermore, the pulled Key snapshot MetaKey3.0 should be a full - volume set containing all the Keys of the configuration items in the micro - application. Therefore, the configuration item Keys of the application version 3.0 in the production environment can be configured according to the Keys recorded in MetaKey3.0.

[0096] Furthermore, based on the micro - application with the Key configuration completed above, assign values to the Keys of each configuration item and establish a production configuration baseline for the corresponding production environment.

[0097] Specifically, determine the Value required for each Key of the micro - application in the production environment according to specific circumstances, and assign each Value to the corresponding Key.

[0098] Furthermore, record the Values configured for the current full set of Keys of the micro - application in the production environment in the form of a snapshot to obtain a production Value snapshot corresponding to the current production environment, label the production Value snapshot with a custom version number, and record it in the production configuration baseline.

[0099] In Figure 1b In a specific example, take a snapshot record of the Values configured for the full set of Keys in the application version 3.0 at this time to obtain a production Value snapshot of the full set of Keys currently in the production environment, name it ConfigZ1.0, and save it to the production configuration baseline to indicate that the production Value snapshot is version 1.0.

[0100] Step S1a-03. During the production stage of the micro-application, in response to determining that any of the parameters is modified, at least one parameter snapshot is added to the current metadata baseline; in response to determining that any of the production parameter values is modified, at least one production parameter value snapshot is added to the production configuration baseline.

[0101] In an embodiment of the present application, based on the production configuration baseline and the Meta baseline of the micro-application determined in the production environment, when the Key and Value of the micro-application configuration item change, the Meta baseline and the production configuration baseline can be updated accordingly.

[0102] In this embodiment, in the production environment during the production stage, if any configuration item of the micro-application changes, or the developer performs any operation on the configuration item, the configuration center records the change of the configuration item as a snapshot with a new version number in the corresponding baseline.

[0103] Specifically, if the developer performs operations such as deletion, modification, or addition on the Key of the micro-application in the production environment, the configuration center will snapshot record the Key of the full set of configuration items of the micro-application again, and obtain 1 Key snapshot with a new version number in the Meta baseline.

[0104] In Figure 1b In a specific example, in the production environment, if any Key of the configuration item in application version 3.0 changes, after the change, the configuration center in the micro-architecture to which micro-application A belongs snapshot records the Key of the full set of configuration items of application version 3.0, obtains 1 new Key snapshot after the change, and names it MetaKey4.0 to indicate that the snapshot of this Key is version 4.0. At this time, the Meta baseline has Key snapshots of three versions, namely MetaKey1.0, MetaKey2.0, Metakey3.0, and MetaKey4.0.

[0105] Further, if the developer performs operations such as deletion, modification, or addition on the Value of any Key in the production environment, the configuration center will snapshot record the Value of the full set of Keys again, and obtain 1 production Value snapshot with a new version number in the production configuration baseline.

[0106] In Figure 1bIn a specific example, if the value of any key in application version 3.0 is changed, the configuration center takes a snapshot of the values of the current configurations of the full set of keys, obtaining a new production value snapshot after the change, naming it ConfigZ2.0 and saving it to the production configuration baseline to indicate that this production value snapshot is of version 2.0. At this time, there are two versions of production value snapshots, ConfigZ1.0 and ConfigZ2.0, in the production configuration baseline.

[0107] In an embodiment of the present application, for a micro-application at any stage and in any environment, if it is found that there is an error in the configuration item of the micro-application, the configuration item of the micro-application can be rolled back using the Meta baseline or the corresponding environment configuration baseline.

[0108] Specifically, taking the production environment in the production stage as an example, since the keys of each configuration item of the micro-application are generated based on the key snapshot of a specific version in the Meta baseline, the keys of the full set of configuration items must be the same as the key snapshot of this specific version. Therefore, if there is a problem with the key of the configuration item in the micro-application, for example, missing the key of a certain configuration item or misconfiguring the key of a certain configuration item, other key snapshots different from the current version can be reselected from the Meta baseline, that is, roll back the currently configured key, and use this key snapshot to reconfigure the key of the configuration item of the micro-application.

[0109] In Figure 1b the example, the keys of each configuration item in application version 3.0 are configured according to the latest version MetaKey4.0 in the Meta baseline. When the key configured for a certain configuration item in application version 3.0 is incorrect and needs to be corrected back to the correct key, an earlier version of the key snapshot, such as MetaKey3.0, can be selected from the Meta baseline, and the keys currently configured for each configuration item are replaced according to the records in Metakey 3.0, completing the rollback operation of the key of the configuration item.

[0110] Furthermore, taking the production environment in the production stage as an example, since the values of each key of the micro-application are recorded in the production configuration baseline in the form of production value snapshots, the assignment of each key must be the same as the production value snapshot of this specific version. Therefore, if there is a problem with the value of the key in the micro-application, for example, missing the assignment of a certain key or misassigning the value of a certain key, other production value snapshots different from the current version can be reselected from the production configuration baseline, that is, roll back the currently configured value, and use this production value snapshot to reassign the key, completing the rollback operation of the key assignment.

[0111] It can be seen that in the rollback operation and the configuration item configuration operations in each environment, the Meta baseline and the corresponding environment configuration baseline can be used as the specifications for configuration management in each stage of the configuration life cycle, and this specification is used to uniformly standardize the configuration items of the micro application.

[0112] It can be seen that the micro application configuration management method according to the embodiments of the present application, based on the Meta baseline and the environment configuration baseline set for the configuration items, comprehensively considers the different configuration life cycles of the relevant configurations, that is, the different relevant configurations of each configuration item in each environment deployed in each stage, to update the Meta baseline and the corresponding environment configuration baseline, so that any modification of any configuration item in any environment can be recorded in the Meta baseline or the corresponding environment configuration baseline, thereby realizing using the Meta baseline and the environment configuration baseline as the specifications for configuration management between each environment. That is to say, in the processes of change, modification, delivery, and rollback of the configuration items, this specification can be used to perform relevant operations on the configuration items, thereby improving the accuracy and efficiency of configuration item management.

[0113] It should be noted that the method according to the embodiments of the present application can be executed by a single device, such as a computer or a server, etc. The method of this embodiment can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In this case of a distributed scenario, one of the multiple devices can only execute one or more steps of the method according to the embodiments of the present application, and these multiple devices will interact with each other to complete the described method.

[0114] It should be noted that some embodiments of the present application have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be executed in a different order from that in the above embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0115] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the embodiments of the present application further provide a micro application configuration management device.

[0116] Referring to Figure 2 , the micro application configuration management device includes:

[0117] The development module 201 is configured to create a metadata baseline during the development stage of the micro application. In the metadata baseline, all current parameters in the micro application are recorded as parameter snapshots; in response to determining that any of the parameters is modified, at least one parameter snapshot is added to the current metadata baseline.

[0118] The initialization production module 202 is configured to, during the production stage of the micro application, configure the parameters of the micro application using the parameter snapshots determined from the current metadata baseline; create a production configuration baseline for the corresponding production stage, and record a production parameter value snapshot in the production configuration baseline, where the production parameter value snapshot includes the production parameter values of all the parameters in the production stage.

[0119] The update production module 203 is configured to, during the production stage of the micro application, in response to determining that any of the parameters is modified, add at least one parameter snapshot to the current metadata baseline, and in response to determining that any of the production parameter values is modified, add at least one production parameter value snapshot to the production configuration baseline.

[0120] As an optional embodiment, the development module 201 is specifically configured to: in each environment deployed during the development stage, select 1 parameter snapshot from the metadata baseline and configure the parameters of the micro application using the selected parameter snapshot.

[0121] In each environment during the development stage, establish an environment configuration baseline for the micro application corresponding to the environment, and record the parameter values of the parameters in the corresponding environment in the environment configuration baseline.

[0122] Furthermore, in each environment during the development stage, fill in the environment parameter values corresponding to the environment for all the parameters.

[0123] In the environment configuration baseline, record the environment parameter values of all the current parameters in the environment as 1 environment parameter value snapshot corresponding to the environment.

[0124] In response to determining that any of the environment parameter values is modified, record the modified all environment parameter values in the environment configuration baseline as 1 new environment parameter value snapshot corresponding to the environment.

[0125] Furthermore, in response to determining that any of the parameters is modified, record the modified all the parameters in the current metadata baseline as 1 new parameter snapshot.

[0126] Furthermore, save the metadata baseline recording all the parameter snapshots to the pre-production library in the delivery stage.

[0127] Configuring parameters for the micro application using a parameter snapshot determined from the current metadata baseline includes:

[0128] Finding the metadata baseline from the pre-production library;

[0129] Selecting a predetermined parameter snapshot from the metadata baseline and performing configuration.

[0130] Further, in response to determining that the parameters currently configured for the micro application are incorrect, select other parameter snapshots in the metadata baseline except the current parameter snapshot, and configure new parameters for the micro application using the selected parameter snapshots;

[0131] In response to an error in the corresponding environment parameter value currently configured for the parameter, select other corresponding environment parameter value snapshots in the corresponding environment configuration baseline except the current parameter value snapshot, and fill in new corresponding environment parameter values for the parameter using the selected corresponding environment parameter value snapshots.

[0132] As an optional embodiment, the initialization production module 202 is specifically configured to:

[0133] Find the Meta baseline corresponding to the micro application from the pre-production library, pull the Key snapshot of the corresponding version number from the found Meta baseline, and configure the configuration items for the micro application in the production environment using the Key reflected in the MetaKey snapshot.

[0134] Wherein, the Key snapshot pulled by the micro application from the Meta baseline at this time can be the Key snapshot of the latest version number, or other Key snapshots that meet the configuration requirements can be pulled according to specific circumstances.

[0135] Further, in the production environment, fill in the environment parameter values corresponding to this environment for all parameters;

[0136] In the environment configuration baseline, record the environment parameter values of all current parameters in this environment as 1 environment parameter value snapshot corresponding to this environment;

[0137] In response to determining that any of the environment parameter values is modified, record the modified all environment parameter values in the environment configuration baseline as 1 new environment parameter value snapshot corresponding to this environment.

[0138] As an optional embodiment, the update production module 203 is specifically configured to:

[0139] In response to determining that any of the production parameter values is modified, record the modified all production parameter values in the production configuration baseline as 1 new production parameter value snapshot.

[0140] In response to determining that the parameters currently configured for the micro-application are incorrect, select other parameter snapshots in the metadata baseline except the current parameter snapshot, and use the selected parameter snapshot to configure new parameters for the micro-application;

[0141] In response to the production parameter value currently configured for the parameter being incorrect, select other production parameter value snapshots in the production configuration baseline except the current parameter value snapshot, and use the selected production parameter value snapshot to fill in a new production parameter value for the parameter.

[0142] For convenience of description, when describing the above device, it is divided into various modules according to functions and described separately. Of course, when implementing the embodiments of the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0143] The device in the above embodiments is used to implement the configuration management method of the corresponding micro-application in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0144] Based on the same inventive concept, corresponding to the method in any of the above embodiments, an embodiment of the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, it implements the configuration management method of the micro-application as described in any of the above embodiments.

[0145] Figure 3 FIG. shows a more specific schematic diagram of the hardware structure of the electronic device provided in this embodiment. The device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. Among them, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are communicatively connected to each other inside the device through the bus 1050.

[0146] The processor 1010 can be implemented in a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, etc., and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0147] The memory 1020 can be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 1020 can store an operating system and other application programs. When implementing the technical solutions provided in the embodiments of the present application through software or firmware, the relevant program codes are stored in the memory 1020 and called and executed by the processor 1010.

[0148] The input / output interface 1030 is used to connect to an input / output module to achieve information input and output. The input / output module can be configured as a component in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Among them, the input device can include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device can include a display, a speaker, a vibrator, an indicator light, etc.

[0149] The communication interface 1040 is used to connect to a communication module (not shown in the figure) to achieve communication interaction between this device and other devices. Among them, the communication module can achieve communication through a wired method (such as USB, network cable, etc.) or through a wireless method (such as a mobile network, WIFI, Bluetooth, etc.).

[0150] The bus 1050 includes a path for transmitting information between various components of the device (such as the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0151] It should be noted that although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device may also only include the components necessary for implementing the solution of the embodiments of the present application, and does not necessarily include all the components shown in the figure.

[0152] The device in the above embodiment is used to implement the configuration management method of the corresponding micro-application in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0153] Based on the same inventive concept, corresponding to the method in any of the above embodiments, the present application also provides a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to cause the computer to execute the configuration management method of the micro-application as described in any of the foregoing embodiments.

[0154] The computer-readable medium of this embodiment includes both permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information that can be accessed by a computing device.

[0155] The computer instructions stored in the storage medium of the above embodiment are used to cause the computer to execute the configuration management method of the micro application as described in any one of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0156] Those of ordinary skill in the art should understand that: the discussion of any of the above embodiments is only exemplary, and is not intended to imply that the scope of the present application (including the claims) is limited to these examples; under the concept of the present application, the technical features in the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations in different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of brevity.

[0157] In addition, for simplicity of explanation and discussion, and in order not to make the embodiments of the present application difficult to understand, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. In addition, the devices may be shown in block diagram form in order to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present application are to be implemented (i.e., these details should be completely within the understanding of those skilled in the art). In the case where specific details (such as circuits) are set forth to describe the exemplary embodiments of the present application, it will be apparent to those skilled in the art that the embodiments of the present application can be implemented without these specific details or with variations of these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0158] Although the present application has been described in connection with specific embodiments thereof, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art in light of the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0159] Embodiments of the present application are intended to cover all such alternatives, modifications, and variations that fall within the broad scope of the appended claims. Accordingly, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the embodiments of the present application shall be included within the protection scope of the present application.

Claims

1. A configuration management method for a micro-application, characterized in that, The method includes: Creating a metadata baseline during the development stage of the micro - application. In the metadata baseline, all current parameters in the micro - application are recorded as parameter snapshots; in response to determining that any of the parameters is modified, at least one parameter snapshot is added to the current metadata baseline; and in each environment deployed during the development stage, one of the parameter snapshots is selected from the metadata baseline, and the parameters of the micro - application are configured using the selected parameter snapshot; wherein recording the parameter values of the parameters corresponding to the environment in the environment configuration baseline includes: In each of the environments during the development stage, filling in the environment parameter values corresponding to the environment for all parameters; In the environment configuration baseline, recording the environment parameter values of all current parameters in the environment as one environment parameter value snapshot corresponding to the environment; In response to determining that any of the environment parameter values is modified, recording the modified all environment parameter values in the environment configuration baseline as one new environment parameter value snapshot corresponding to the environment; In each of the environments during the development stage, establishing an environment configuration baseline corresponding to the environment for the micro - application, and recording the parameter values of the parameters corresponding to the environment in the environment configuration baseline; During the production stage of the micro - application, configuring the parameters of the micro - application using the parameter snapshots determined from the current metadata baseline; creating a production configuration baseline corresponding to the production stage, and recording production parameter value snapshots in the production configuration baseline, where the production parameter value snapshots include the production parameter values of all parameters in the production stage; During the production stage of the micro - application, in response to determining that any of the parameters is modified, at least one parameter snapshot is added to the current metadata baseline, and in response to determining that any of the production parameter values is modified, at least one production parameter value snapshot is added to the production configuration baseline.

2. The method according to claim 1, wherein In any stage of the micro - application, it further includes: In response to determining that the parameters currently configured in the micro - application are incorrect, selecting other parameter snapshots except the current parameter snapshot from the metadata baseline, and configuring new parameters for the micro - application using the selected parameter snapshots; In response to the production parameter values currently configured for the parameters being incorrect, selecting other production parameter value snapshots except the current production parameter value snapshot from the production configuration baseline, and filling in new production parameter values for the parameters using the selected production parameter value snapshots.

3. The method according to claim 1, wherein In any stage of the micro - application, the step of, in response to determining that any of the parameters is modified, adding at least one parameter snapshot to the current metadata baseline includes: In response to determining that any of the parameters is modified, recording the modified all parameters in the current metadata baseline as one new parameter snapshot.

4. The method according to claim 1, characterized in that, After the micro - application completes the development stage and before entering the production stage, it further includes: Saving the metadata baseline recording all the parameter snapshots to a pre - production library in the delivery stage; The step of configuring the parameters of the micro - application using the parameter snapshots determined from the current metadata baseline includes: Finding the metadata baseline from the pre - production library; Select a predetermined snapshot of the parameter from the metadata baseline and configure it.

5. The method according to claim 1, characterized in that, In response to determining that any of the production parameter values is modified, add at least one snapshot of the production parameter value in the production configuration baseline, including: In response to determining that any of the production parameter values is modified, record all the modified production parameter values as 1 new snapshot of the production parameter value in the production configuration baseline.

6. A configuration management device for a micro-application, characterized in that, Include: A development module, configured to create a metadata baseline during the development stage of the micro-application. In the metadata baseline, record all the current parameters in the micro-application as parameter snapshots; in response to determining that any of the parameters is modified, add at least one parameter snapshot in the current metadata baseline; And in each environment deployed during the development stage, select 1 parameter snapshot from the metadata baseline and configure the parameters for the micro-application using the selected parameter snapshot; Wherein recording the parameter values of the parameters in the corresponding environment in the environment configuration baseline includes: In each environment during the development stage, fill in the environment parameter values corresponding to the environment for all the parameters; In the environment configuration baseline, record the environment parameter values of all the current parameters in this environment as 1 snapshot of the environment parameter value corresponding to this environment; In response to determining that any of the environment parameter values is modified, record all the modified environment parameter values as 1 new snapshot of the environment parameter value corresponding to this environment in the environment configuration baseline; In each environment during the development stage, establish an environment configuration baseline corresponding to this environment for the micro-application and record the parameter values of the parameters in the corresponding environment in the environment configuration baseline; An initialization production module, configured to, during the production stage of the micro-application, configure the parameters for the micro-application using the parameter snapshots determined from the current metadata baseline; create a production configuration baseline corresponding to the production stage and record snapshots of the production parameter values in the production configuration baseline, where the snapshots of the production parameter values include the production parameter values of all the parameters in the production stage; An update production module, configured to, during the production stage of the micro-application, in response to determining that any of the parameters is modified, add at least one parameter snapshot in the current metadata baseline, and in response to determining that any of the production parameter values is modified, add at least one snapshot of the production parameter value in the production configuration baseline.

7. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executed by the processor, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1 to 5.

8. A non-transitory computer-readable storage medium, characterized in that, The non-transitory computer-readable storage medium stores computer instructions for causing a computer to execute the method according to any one of claims 1 to 5.

Images