A model deployment method and device based on model migration, equipment and medium
By parsing model packages and configuring databases, the problem of low model deployment efficiency in low-code modeling tools is solved, achieving efficient model deployment and enhanced scalability.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- INSPUR GENERSOFT CO LTD
- Filing Date
- 2022-08-23
- Publication Date
- 2026-07-14
AI Technical Summary
Existing low-code modeling tools lack dedicated model deployment tools and do not support the extension of the model deployment process, resulting in low model migration efficiency.
This paper presents a model deployment method based on model migration, which achieves efficient deployment of model content through model package parsing, extended list generation, and database configuration.
It improves the performance of model information query and loading, enhances the scalability of the deployment process, and supports the parsing of model content and the expansion of the deployment process.
Smart Images
Figure CN115202730B_ABST
Abstract
Description
Technical Field
[0001] This specification relates to the field of computer technology, and in particular to a model deployment method, apparatus, device and medium based on model migration. Background Technology
[0002] With the development of development technologies, enterprises are placing increasing emphasis on low-code business modeling during their digital transformation. In the field of low-code modeling, model migration refers to moving the developed business model from the development environment to the runtime environment. Existing low-code modeling tools or platforms only provide basic support for the model migration process, generally do not offer dedicated model deployment tools, and do not support the extension of the model deployment process. Summary of the Invention
[0003] This specification provides one or more embodiments of a model deployment method, apparatus, device, and medium based on model migration to address the technical problems raised in the background art.
[0004] One or more embodiments of this specification employ the following technical solutions:
[0005] This specification provides one or more embodiments of a model deployment method based on model migration, including:
[0006] During the migration of a specified model, the specified model is packaged into a model package;
[0007] The model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed;
[0008] The model content to be deployed is compared with the model content pre-stored in the database to obtain an expanded list;
[0009] The database is configured by extending the extended list to obtain the configured database.
[0010] Based on the description information, the content of the model to be deployed is deployed to the configured database.
[0011] Optionally, the description information includes the model package name, model package version, model dependencies, and a list of models contained in the model package.
[0012] Optionally, deploying the content of the model to be deployed to the configured database according to the description information specifically includes:
[0013] Based on the model dependencies, the content of the models to be deployed is sorted.
[0014] The sorted model content to be deployed is deployed to the configured database.
[0015] Optionally, before comparing the model content to be deployed with the model content pre-stored in the database to obtain the expanded list, the method further includes:
[0016] The model content is parsed to obtain the model dependencies and the content contained in the model.
[0017] Optionally, the extension list may include one or more of the following: deleting extensions, adding extensions, and updating extensions.
[0018] Optionally, comparing the model content to be deployed with the model content pre-stored in the database to obtain an expanded list specifically includes:
[0019] Determine whether the content of the model to be deployed is the same as the content of the model pre-stored in the database;
[0020] If the database contains model content not included in the model package, a deletion extension is performed;
[0021] If the model package contains model content not included in the database, a new extension is obtained;
[0022] If the version of the model content in the model package is higher than the version of the model content in the database, an update extension is obtained.
[0023] Optionally, the step of configuring the database according to the extended list specifically includes:
[0024] If the extension list includes extensions to be deleted, the corresponding model content to be deleted is read from the database and the model content to be deleted is deleted.
[0025] If the extension list includes a new extension, the model dependency is determined through the description information and the model dependency is saved to the database. The configuration data corresponding to the new extension is determined and the configuration data corresponding to the new extension is saved to the database.
[0026] If the extension list includes an updated extension, determine the configuration data corresponding to the updated extension and save the configuration data corresponding to the updated extension to the database.
[0027] This specification provides one or more embodiments of a model deployment apparatus based on model migration, the apparatus comprising:
[0028] The packaging unit packages the specified model into a model package during the specified model migration process;
[0029] The parsing unit parses the model package using a pre-acquired model deployment tool to obtain description information and the model content to be deployed;
[0030] The comparison unit compares the model content to be deployed with the model content pre-stored in the database to obtain an expanded list;
[0031] The extended configuration unit extends the configuration of the database according to the extended list to obtain the configured database;
[0032] The deployment unit deploys the content of the model to be deployed to the configured database according to the description information.
[0033] This specification provides one or more embodiments of a model deployment device based on model migration, comprising:
[0034] At least one processor; and,
[0035] A memory communicatively connected to the at least one processor; wherein,
[0036] The memory stores instructions that can be executed by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
[0037] During the migration of a specified model, the specified model is packaged into a model package;
[0038] The model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed;
[0039] The model content to be deployed is compared with the model content pre-stored in the database to obtain an expanded list;
[0040] The database is configured by extending the extended list to obtain the configured database.
[0041] Based on the description information, the content of the model to be deployed is deployed to the configured database.
[0042] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:
[0043] During the migration of a specified model, the specified model is packaged into a model package;
[0044] The model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed;
[0045] The model content to be deployed is compared with the model content pre-stored in the database to obtain an expanded list;
[0046] The database is configured by extending the extended list to obtain the configured database.
[0047] Based on the description information, the content of the model to be deployed is deployed to the configured database.
[0048] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:
[0049] This specification proposes a method for low-code model parsing and deployment: 1) The model content is parsed in advance during the deployment process and directly deployed to the database table, improving the performance of runtime model information query and loading; 2) Extensions are provided during the deployment process to support extensions at different stages, greatly improving the scalability of the deployment process. Attached Figure Description
[0050] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:
[0051] Figure 1 A flowchart illustrating a model deployment method based on model migration provided for one or more embodiments of this specification;
[0052] Figure 2 A schematic diagram of the model package deployment framework provided in one or more embodiments of this specification;
[0053] Figure 3 A flowchart illustrating the deployment process of a model package provided in one or more embodiments of this specification;
[0054] Figure 4 A schematic diagram of the structure of a model deployment device based on model migration provided for one or more embodiments of this specification;
[0055] Figure 5 This is a schematic diagram of the structure of a model deployment device based on model migration, provided for one or more embodiments of this specification. Detailed Implementation
[0056] This specification provides a model deployment method, apparatus, device, and medium based on model migration.
[0057] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.
[0058] Figure 1 This document illustrates a flowchart of a model deployment method based on model migration, provided for one or more embodiments. This process can be executed by a model deployment system, which can deploy the model during the migration process. Certain input parameters or intermediate results in the process can be manually adjusted to help improve accuracy.
[0059] The method flow steps of the embodiments in this specification are as follows:
[0060] S102, During the specified model migration process, the specified model is packaged into a model package.
[0061] In the embodiments described in this specification, the specified model is packaged into a model package, which reflects the integrity and encapsulation of model migration. The model package is the carrier of model content migration and the input of the model deployment tool. The model package may contain model package description information and model content.
[0062] In the embodiments of this specification, the descriptive information may include the model package name, model package version, model dependencies, and a list of models contained in the model package.
[0063] S104, the model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed.
[0064] In the embodiments described in this specification, based on the model package, the model deployment tool reads the model package file and parses the model package description information and model content. Among these...
[0065] Based on the model package description information, the dependency information of all model packages to be deployed is parsed. Model packages with dependencies are sorted according to their dependencies, while model packages without dependencies can be placed at the end of the sequence.
[0066] The model content is loaded one by one and parsed. Basic model information, model dependency information, and detailed model content are parsed into memory.
[0067] S106, compare the model content to be deployed with the model content pre-stored in the database to obtain an expanded list.
[0068] In the embodiments of this specification, before comparing the model content to be deployed with the model content pre-stored in the database to obtain the expanded list, the model content can be parsed in advance to obtain the model dependencies and the content contained in the model. Then, based on the model dependencies and the content contained in the model, the model content to be deployed is compared with the model content pre-stored in the database to obtain the expanded list.
[0069] In the embodiments of this specification, when comparing the model content to be deployed with the model content pre-stored in the database to obtain the extension list, it can first be determined whether the model content to be deployed is the same as the model content pre-stored in the database, and then the extension list can be obtained. The extension list can include one or more of the following: deleting extensions, adding extensions, and updating extensions. If the database contains model content not included in the model package, the extension is deleted; if the model package contains model content not included in the database, the extension is added; if the version of the model content in the model package is higher than the version of the model content in the database, the extension is updated.
[0070] Furthermore, the resulting extended table can include a deletion list, an addition list, and an update list. First, it can be determined whether to perform a deletion extension. If yes, then the deletion extension is performed; if no, it can be determined whether to perform an addition extension. If yes, then the addition extension is performed; if no, it can be determined whether to perform an update extension. If yes, then the update extension is performed; if no, the model content is saved to the database.
[0071] S108, The database is extended according to the extended list to obtain the configured database.
[0072] In the embodiments of this specification, when configuring the database according to the extension list, if the extension list includes deleting an extension, the corresponding model content to be deleted is read from the database and the model content to be deleted is deleted; if the extension list includes adding an extension, the model dependency is determined through the description information and the model dependency is saved to the database, the configuration data corresponding to the added extension is determined and the configuration data corresponding to the added extension is saved to the database; if the extension list includes updating an extension, the configuration data corresponding to the updated extension is determined and the configuration data corresponding to the updated extension is saved to the database.
[0073] S110, based on the description information, deploy the content of the model to be deployed to the configured database.
[0074] In the embodiments of this specification, during model deployment, the model content to be deployed is sorted according to the model dependencies; the sorted model content to be deployed is then deployed to the configured database.
[0075] It should be noted that the embodiments of this specification disclose a method for parsing and deploying a low-code modeling model, specifically used to support model content parsing, model deployment process extension, and model content storage in the database during the low-code modeling model migration process.
[0076] The embodiments in this specification aim to address the challenges in the low-code modeling field, specifically during model migration. They provide a low-code model parsing and deployment method that supports parsing model content into a database, improving runtime model information loading performance; and supports model deployment process extension, enhancing the scalability of the deployment process.
[0077] The embodiments in this specification have the following features:
[0078] 1. The model deployment depends on the model package, and the model package is parsed and deployed.
[0079] 2. Analyze the model content, expand the internal details of the model, and store the model in the database;
[0080] 3. Supports extensions to the model deployment process, such as: supporting the generation of configuration data based on model content during deployment; supporting the synchronous runtime customization of content based on model content;
[0081] Compared with existing technologies, the embodiments of this specification propose a method for low-code model parsing and deployment: 1) The model content is parsed in advance during the deployment process and directly deployed to the database table, improving the performance of runtime model information query and loading; 2) Extensions are provided during the deployment process to support extensions at different stages, greatly improving the scalability of the deployment process.
[0082] The embodiments in this specification can be implemented through the following specific technical solutions:
[0083] 1. During the model migration process, the model exists as a model package file.
[0084] During model migration, the model is packaged into a model package, which embodies the integrity and encapsulation of the model migration process. The model package serves as the carrier for the model content migration and is the input to the model deployment tool. The model package contains the following information: model package description information and model content. The following is a detailed explanation of the model package description information.
[0085]
[0086] 2. The model deployment tool supports parsing model package contents and model parsing.
[0087] Based on the model package, the model deployment tool reads the model package file and parses the model package description information and model content.
[0088] a) Based on the model package description information, parse the dependency information of all packages to be deployed. Packages with dependencies are sorted according to their dependencies, and packages without dependencies are placed at the end of the sequence.
[0089] b) Load the model content one by one and parse it. Parse out the basic model information, model dependency information, and detailed model content into memory.
[0090] 3. Supports model deployment scaling
[0091] During model deployment, there are specific requirements for model processing, such as the ability to extend the model deployment process, for example, to parse model dependencies and save them to the database, to parse model content to generate configuration data and save it to the database, and to synchronize runtime customized content.
[0092] During the deployment process, the deployment tool compares the model package with the model packages that already exist in the database to obtain the model deletion list, addition list, and update list; for different lists, it performs model deployment extension steps.
[0093] a) Model deletion extension: Execute the deletion extension, read the model content from the database, perform deletion checks, and confirm whether deletion is possible; delete the content generated by the extension during the previous deployment process.
[0094] b) Adding new extensions to the model: Execute new extensions, such as resolving model dependencies and saving them to the database, generating configuration data and saving it to the database.
[0095] c) Model update extension: Execute update extensions, such as synchronizing runtime-customized content, generating configuration data, and updating the database.
[0096] The extension actions in each of the above types of extensions can be orchestrated through configuration. For example, when adding a new extension, you can configure two actions: resolving model dependencies and saving them to the database, and generating configuration data and saving it to the database. You can also add other actions. During deployment, the deployment tool provides extension points for developers. The embodiments in this specification can provide an extension mechanism, but the specific processing procedures for extension actions are not described in detail in these embodiments.
[0097] 4. Supports deploying models from the model package to a specified database table.
[0098] During model migration, the model is packaged into a model package, which reflects the integrity and encapsulation of the model migration. At runtime, it is also necessary to parse the information contained in the model, such as to obtain model dependency information, which requires good performance.
[0099] The model itself is laid flat from the package to the database table, avoiding the complex process of parsing the package again and improving the performance of model lookup and loading; during the expansion process, some model content information is parsed, which can support direct query and use from the database, avoiding parsing the model content again.
[0100] 5. The deployment process supports transactions at the model package level. This means that the parsing and deployment of models within the same model package will either succeed for all models in the package or fail for none of them. There is no possibility of partial success in the parsing and deployment of the same model package.
[0101] Furthermore, Figure 2 This is a schematic diagram of the model package deployment framework provided in the embodiments of this specification. In the diagram, the models are packaged into model packages and deployed to the database through a model deployment tool.
[0102] Furthermore, Figure 3 The flowchart for deploying model packages provided in the embodiments of this specification is as follows: First, the model packages are deployed. Then, the model packages to be deployed are sorted according to their dependency order. Next, the model package content is parsed to obtain all models in the package. Then, the model change sets are obtained: deleted models, added models, and updated models. Here, deleted models, added models, and updated models correspond to the deleted list, added list, and updated list of models, respectively. Then, it is determined whether to execute a deletion extension. If yes, the deletion extension is executed; otherwise, it is determined whether to execute an added extension. If yes, the added extension is executed; otherwise, it is determined whether to execute an update extension. If yes, the update extension is executed, and then the model content is saved to the database. Otherwise, the model content is directly saved to the database.
[0103] Figure 4 This specification provides a schematic diagram of a model deployment device based on model migration, which includes: a packaging unit 402, a parsing unit 404, a comparison unit 406, an extended configuration unit 408, and a deployment unit 410, according to one or more embodiments of this specification.
[0104] Packaging unit 402 packages the specified model into a model package during the specified model migration process;
[0105] The parsing unit 404 parses the model package using a pre-acquired model deployment tool to obtain description information and the model content to be deployed;
[0106] The comparison unit 406 compares the model content to be deployed with the model content pre-stored in the database to obtain an expanded list;
[0107] The extended configuration unit 408 performs extended configuration on the database according to the extended list to obtain the configured database.
[0108] Deployment unit 410 deploys the content of the model to be deployed to the configured database according to the description information.
[0109] Figure 5 A schematic diagram of a model deployment device based on model migration, provided for one or more embodiments of this specification, includes:
[0110] At least one processor; and,
[0111] A memory communicatively connected to the at least one processor; wherein,
[0112] The memory stores instructions that can be executed by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:
[0113] During the migration of a specified model, the specified model is packaged into a model package;
[0114] The model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed;
[0115] The model content to be deployed is compared with the model content pre-stored in the database to obtain an expanded list;
[0116] The database is configured by extending the extended list to obtain the configured database.
[0117] Based on the description information, the content of the model to be deployed is deployed to the configured database.
[0118] This specification provides one or more embodiments of a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:
[0119] During the migration of a specified model, the specified model is packaged into a model package;
[0120] The model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed;
[0121] The model content to be deployed is compared with the model content pre-stored in the database to obtain an expanded list;
[0122] The database is configured by extending the extended list to obtain the configured database.
[0123] Based on the description information, the content of the model to be deployed is deployed to the configured database.
[0124] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.
[0125] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0126] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.
Claims
1. A model deployment method based on model transfer, characterized in that, The method includes: During the migration of a specified model, the specified model is packaged into a model package; The model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed; The model content to be deployed is compared with the model content pre-stored in the database to obtain an expanded list; The database is configured by extending the extended list to obtain the configured database. Based on the description information, the content of the model to be deployed is deployed to the configured database; Before comparing the model content to be deployed with the model content pre-stored in the database to obtain the expanded list, the method further includes: The model content is parsed to obtain the model dependencies and the content contained in the model; The extension list includes one or more of the following: deleted extensions, added extensions, and updated extensions; The step of comparing the model content to be deployed with the model content pre-stored in the database to obtain an expanded list specifically includes: Determine whether the content of the model to be deployed is the same as the content of the model pre-stored in the database; If the database contains model content not included in the model package, a deletion extension is performed; If the model package contains model content not included in the database, a new extension is obtained; If the version of the model content in the model package is higher than the version of the model content in the database, an update extension is obtained; The step of configuring the database according to the extended list specifically includes: If the extension list includes extensions to be deleted, the corresponding model content to be deleted is read from the database and the model content to be deleted is deleted. If the extension list includes a new extension, the model dependency is determined through the description information and the model dependency is saved to the database. The configuration data corresponding to the new extension is determined and the configuration data corresponding to the new extension is saved to the database. If the extension list includes an updated extension, determine the configuration data corresponding to the updated extension and save the configuration data corresponding to the updated extension to the database.
2. The method according to claim 1, characterized in that, The description information includes the model package name, model package version, model dependencies, and a list of models contained in the model package.
3. The method according to claim 2, characterized in that, The step of deploying the content of the model to be deployed to the configured database according to the description information specifically includes: Based on the model dependencies, the content of the models to be deployed is sorted. The sorted model content to be deployed is deployed to the configured database.
4. A model deployment device based on model transfer, characterized in that, The device includes: The packaging unit packages the specified model into a model package during the specified model migration process; The parsing unit parses the model package using a pre-acquired model deployment tool to obtain description information and the model content to be deployed; The comparison unit compares the model content to be deployed with the model content pre-stored in the database to obtain an expanded list; The extended configuration unit extends the configuration of the database according to the extended list to obtain the configured database; The deployment unit deploys the content of the model to be deployed to the configured database according to the description information; Before comparing the model content to be deployed with the model content pre-stored in the database to obtain the expanded list, the process also includes: The model content is parsed to obtain the model dependencies and the content contained in the model; The extension list includes one or more of the following: deleted extensions, added extensions, and updated extensions; The step of comparing the model content to be deployed with the model content pre-stored in the database to obtain an expanded list specifically includes: Determine whether the content of the model to be deployed is the same as the content of the model pre-stored in the database; If the database contains model content not included in the model package, a deletion extension is performed; If the model package contains model content not included in the database, a new extension is obtained; If the version of the model content in the model package is higher than the version of the model content in the database, an update extension is obtained; The step of configuring the database according to the extended list specifically includes: If the extension list includes extensions to be deleted, the corresponding model content to be deleted is read from the database and the model content to be deleted is deleted. If the extension list includes a new extension, the model dependency is determined through the description information and the model dependency is saved to the database. The configuration data corresponding to the new extension is determined and the configuration data corresponding to the new extension is saved to the database. If the extension list includes an updated extension, determine the configuration data corresponding to the updated extension and save the configuration data corresponding to the updated extension to the database.
5. A model deployment device based on model transfer, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to: During the migration of a specified model, the specified model is packaged into a model package; The model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed; The model content to be deployed is compared with the model content pre-stored in the database to obtain an expanded list; The database is configured by extending the extended list to obtain the configured database. Based on the description information, the content of the model to be deployed is deployed to the configured database; Before comparing the model content to be deployed with the model content pre-stored in the database to obtain the expanded list, the process also includes: The model content is parsed to obtain the model dependencies and the content contained in the model; The extension list includes one or more of the following: deleted extensions, added extensions, and updated extensions; The step of comparing the model content to be deployed with the model content pre-stored in the database to obtain an expanded list specifically includes: Determine whether the content of the model to be deployed is the same as the content of the model pre-stored in the database; If the database contains model content not included in the model package, a deletion extension is performed; If the model package contains model content not included in the database, a new extension is obtained; If the version of the model content in the model package is higher than the version of the model content in the database, an update extension is obtained; The step of configuring the database according to the extended list specifically includes: If the extension list includes extensions to be deleted, the corresponding model content to be deleted is read from the database and the model content to be deleted is deleted. If the extension list includes a new extension, the model dependency is determined through the description information and the model dependency is saved to the database. The configuration data corresponding to the new extension is determined and the configuration data corresponding to the new extension is saved to the database. If the extension list includes an updated extension, determine the configuration data corresponding to the updated extension and save the configuration data corresponding to the updated extension to the database.
6. A non-volatile computer storage medium, characterized in that, The computer-executable instructions are stored thereon and are configured as follows: During the migration of a specified model, the specified model is packaged into a model package; The model package is parsed using a pre-acquired model deployment tool to obtain description information and the model content to be deployed; The model content to be deployed is compared with the model content pre-stored in the database to obtain an expanded list; The database is configured by extending the extended list to obtain the configured database. Based on the description information, the content of the model to be deployed is deployed to the configured database; Before comparing the model content to be deployed with the model content pre-stored in the database to obtain the expanded list, the process also includes: The model content is parsed to obtain the model dependencies and the content contained in the model; The extension list includes one or more of the following: deleted extensions, added extensions, and updated extensions; The step of comparing the model content to be deployed with the model content pre-stored in the database to obtain an expanded list specifically includes: Determine whether the content of the model to be deployed is the same as the content of the model pre-stored in the database; If the database contains model content not included in the model package, a deletion extension is performed; If the model package contains model content not included in the database, a new extension is obtained; If the version of the model content in the model package is higher than the version of the model content in the database, an update extension is obtained; The step of configuring the database according to the extended list specifically includes: If the extension list includes extensions to be deleted, the corresponding model content to be deleted is read from the database and the model content to be deleted is deleted. If the extension list includes a new extension, the model dependency is determined through the description information and the model dependency is saved to the database. The configuration data corresponding to the new extension is determined and the configuration data corresponding to the new extension is saved to the database. If the extension list includes an updated extension, determine the configuration data corresponding to the updated extension and save the configuration data corresponding to the updated extension to the database.