A metadata dynamic deployment method, device, equipment and medium

Abstract

The embodiment of the specification discloses a metadata dynamic deployment method, device, equipment and medium, the method comprises: obtaining a new project of a preset designer, and binding the new project with a preset distributed version control system; wherein the preset distributed version control system controls the branch and historical version of metadata; the corresponding metadata branch in the preset distributed version control system is mapped to the preset database based on the preset designer, and the metadata branch in the preset database is decrypted by the preset designer; the metadata branch in the preset database is processed based on a preset program to obtain a metadata resource file, so as to publish and deploy the metadata resource file to the development environment corresponding to the new project.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a method, apparatus, device, and medium for the dynamic deployment of metadata. Background Technology

[0002] In recent years, Enterprise Resource Planning (ERP) software in traditional industries has undergone significant changes, with enterprises placing greater demands and exploring more diverse use cases for development systems and project patch files. However, unlike business systems, development systems are not standalone systems; rather, they function more like management systems, providing unified metadata processing services for various business systems. Given the sensitivity of project metadata, ensuring the security of metadata within development systems and project patch files to safeguard enterprise digital security is a crucial issue that project development and deployment systems must address and consider.

[0003] In existing technologies, during project development and system deployment, distributed version control systems are often coupled with the designer. This means that the metadata managed by the distributed version control system directly faces the developers, resulting in low efficiency and long processing times when developers need to search, combine, and update from large amounts of metadata. This makes it difficult to meet the efficiency requirements of the development system, and when metadata is directly exposed to developers, it is difficult to ensure the secure deployment of metadata and achieve unified and effective development management. Summary of the Invention

[0004] To address the aforementioned technical problems, this specification provides one or more embodiments of a method, apparatus, device, and medium for the dynamic deployment of cloud data.

[0005] One or more embodiments of this specification employ the following technical solutions:

[0006] This specification provides one or more embodiments of a method for dynamically deploying metadata, the method comprising:

[0007] Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata;

[0008] The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer;

[0009] The metadata branches in the pre-set database are processed according to a preset program to obtain metadata resource files, which are then published and deployed to the development environment corresponding to the newly created project.

[0010] Optionally, in one or more embodiments of this specification, before obtaining the new project from the preset designer and binding the new project to the preset distributed version control system, the method further includes:

[0011] The metadata is encrypted based on a preset encryption strategy to obtain encrypted metadata, and the encrypted metadata is managed and controlled through a preset distributed version control system.

[0012] Specifically, the step of encrypting the metadata based on a preset encryption strategy to obtain encrypted metadata includes:

[0013] Obtain one or more resource information corresponding to each of the metadata branches in the threshold distributed version control system, and construct the access structure of each metadata branch based on the inclusion relationship of the one or more resource information;

[0014] Based on the master public key of each metadata branch and the access structure of each metadata branch, each metadata branch is encrypted to obtain the encrypted metadata.

[0015] Optionally, in one or more embodiments of this specification, decrypting the metadata branch in the preset database through the preset designer specifically includes:

[0016] Obtain the current project corresponding to the preset designer, and monitor and obtain the resource information of the current project operation;

[0017] Obtain the master private key of the preset designer, and decrypt the metadata branch in the preset database based on the master private key and the resource information of the current project operation;

[0018] If the master private key corresponds to the master public key and the resource information of the current project operation conforms to the access structure, then the decryption of the metadata branch in the preset database is realized.

[0019] Optionally, in one or more embodiments of this specification, after decrypting the metadata branch in the preset database through the preset designer, the method further includes:

[0020] Based on the current project corresponding to the newly created project, determine the metadata to be changed in the preset database;

[0021] The metadata in the preset database is modified by the preset designer to obtain modified metadata; wherein, the modified metadata includes: undo metadata, add metadata, and transform metadata;

[0022] The modified metadata is synchronized to the distributed version control system via the preset designer.

[0023] Optionally, in one or more embodiments of this specification, after obtaining the changed metadata by modifying the metadata in the preset database through the preset designer, the method further includes:

[0024] The metadata branch containing the changed metadata in the preset database is processed according to a preset program to obtain a metadata patch resource file;

[0025] The metadata patch resource file is deployed to the development environment corresponding to the newly created project using a pre-built patching tool.

[0026] Optionally, in one or more embodiments of this specification, after processing the metadata branch containing the changed metadata in the preset database according to a preset program to obtain a metadata patch resource file, the method further includes:

[0027] The metadata patch resource file is published according to a preset procedure;

[0028] By analyzing the changed metadata in the published metadata patch resource file, the problem patch corresponding to the current project is identified, and the problem patch is updated and upgraded to achieve the processing and repair of the current project.

[0029] Optionally, in one or more embodiments of this specification, after obtaining the new project from the preset designer and binding the new project to the preset distributed version control system, the method further includes:

[0030] Determine whether there is a metadata dependency between the newly created project and the pre-built distributed version control system;

[0031] If it exists, the metadata dependency is obtained and written into the new project to process the metadata dependency.

[0032] This specification provides one or more embodiments of a dynamic metadata deployment apparatus, the apparatus comprising:

[0033] Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata;

[0034] The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer;

[0035] The metadata branches in the pre-set database are processed according to a preset program to obtain metadata resource files, which are then deployed to the development environment corresponding to the newly created project.

[0036] This specification provides one or more embodiments of a cloud data dynamic deployment device, the device comprising:

[0037] At least one processor; and,

[0038] A memory communicatively connected to the at least one processor; wherein,

[0039] 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:

[0040] Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata;

[0041] The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer;

[0042] The metadata branches in the pre-set database are processed according to a preset program to obtain metadata resource files, which are then deployed to the development environment corresponding to the newly created project.

[0043] 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:

[0044] Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata;

[0045] The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer;

[0046] The metadata branches in the pre-set database are processed according to a preset program to obtain metadata resource files, which are then deployed to the development environment corresponding to the newly created project.

[0047] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

[0048] By adding a database as a transit center for metadata processing to the designer and the pre-built distributed version control system, the corresponding metadata branches in the pre-built distributed version control system are mapped to the pre-built database based on the pre-built designer. This decouples the pre-built distributed version control system from the designer, solving the problem of low efficiency in batch searching and combining updates of a large amount of metadata when the metadata in the existing distributed version control system directly faces the developers. Attached Figure Description

[0049] 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:

[0050] Figure 1 A schematic diagram of a method flow for dynamically deploying metadata provided in an embodiment of this specification;

[0051] Figure 2 A schematic diagram illustrating the deployment process of a dynamic metadata deployment method provided in this embodiment of the specification;

[0052] Figure 3 A schematic diagram of the internal structure of a dynamic metadata deployment device provided in an embodiment of this specification;

[0053] Figure 4 A schematic diagram of the internal structure of a metadata dynamic deployment device provided in an embodiment of this specification;

[0054] Figure 5 This is a schematic diagram of the internal structure of a non-volatile storage medium provided in the embodiments of this specification. Detailed Implementation

[0055] This specification provides an embodiment of a method, apparatus, device, and medium for the dynamic deployment of metadata.

[0056] 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.

[0057] like Figure 1 As shown, this specification provides a flowchart illustrating a method for dynamically deploying metadata, through one or more embodiments. Figure 1 As can be seen, in one or more embodiments of this specification, a method for dynamically deploying metadata includes the following steps:

[0058] S101: Obtain the newly created project from the pre-built designer and bind the newly created project to the pre-built distributed version control system; wherein, the pre-built distributed version control system controls the branching and historical versions of metadata.

[0059] To enable the pre-built designer to retrieve metadata from a pre-built distributed version control system, achieving unified and effective development of the development system, one or more embodiments of this specification first obtain a newly created project from a pre-set designer, where the pre-set designer is the part that actually operates on the metadata. After obtaining the newly created project from the pre-set designer, the new project is bound to the pre-built distributed version control system, thereby enabling the pre-built designer to subsequently obtain metadata from the pre-built distributed version control system for publishing and deployment. It should be noted that in one or more embodiments of this specification, the pre-built distributed version control system is a Git repository capable of effectively and quickly handling version management for projects ranging from very small to very large, and uses this distributed version control system to control and manage branches and historical versions of metadata.

[0060] Furthermore, to ensure the security of metadata and avoid security issues arising from the display of sensitive metadata, in one or more embodiments of this specification, before obtaining the newly created project from the pre-built designer and binding the new project to the pre-built distributed version control system, the method further includes the following process:

[0061] Metadata is encrypted using a preset encryption strategy to obtain encrypted metadata, which is then managed and controlled through a pre-built distributed version control system. The metadata obtained through this process is encrypted, avoiding the security issues associated with directly displaying metadata. Specifically, encrypting metadata using a preset encryption strategy involves the following steps: obtaining one or more resource information corresponding to each metadata branch in the threshold distributed version control system, and constructing an access structure for each metadata branch based on the inclusion relationship of the resource information. Then, each metadata branch is encrypted according to its master public key and access structure to obtain encrypted metadata. It should be noted that the master public key can be pre-assigned to each metadata branch by the server, and the corresponding master private key is assigned to the corresponding designer.

[0062] Furthermore, in one or more embodiments of this specification, after obtaining a new project from the preset designer and binding the new project to the preset distributed version control system, the method further includes:

[0063] Determine whether there is a metadata dependency between the newly created project and the pre-built distributed version control system. If so, in order to ensure the normal operation of the system, obtain the metadata dependency and write it into the newly created project to handle the metadata dependency.

[0064] S102: Map the corresponding metadata branch in the preset distributed version control system to the preset database based on the preset designer, and decrypt the metadata branch in the preset database through the preset designer.

[0065] To avoid coupling the pre-built distributed version control system with the designer, which would cause the metadata in the distributed version control system to directly face the developers, resulting in low efficiency in operations such as batch searching and combining updates of large amounts of metadata. Figure 2 As shown in the embodiments of this specification, a database is introduced as a transit center for metadata processing. The corresponding metadata branches in the pre-built distributed version control system are mapped to the pre-built database based on the pre-built designer, significantly reducing batch file lookups and updates, and simplifying metadata operations. Then, the metadata branches in the pre-built database are decrypted through the pre-built designer. Since the metadata is encrypted, metadata security is achieved. The designer has a corresponding decryption method, and it can only be displayed through the designer, improving the reliability of the metadata deployment process.

[0066] Furthermore, decrypting the metadata branch in the pre-configured database using the pre-configured designer involves the following process: First, the current project corresponding to the pre-configured designer is obtained to monitor and acquire the resource information of the current project's operations. Then, the master private key of the pre-configured designer is obtained, and the metadata branch in the pre-configured database is decrypted based on the master private key and the resource information of the current project's operations. If the master private key and master public key correspond and the resource information of the current project's operations conforms to the access structure specified by the encryption policy, then the metadata branch in the pre-configured database is decrypted. In other words, the metadata managed by the distributed version control system is encrypted using a special encryption method. As mentioned above, the accessible resource information is restricted based on the access structure, and the encrypted metadata is obtained based on the master public key. Only the designer with the corresponding resource information and the corresponding master private key can decrypt and display the metadata, ensuring data security.

[0067] Furthermore, after decrypting the metadata branches in the pre-built database using the pre-built designer, the method also includes:

[0068] Based on the current project corresponding to the newly created project, the metadata to be modified in the pre-built database is determined. Then, the metadata in the pre-built database is modified using the pre-built designer to obtain the modified metadata; simultaneously, the modified metadata is synchronized to the distributed version control system using the pre-built designer. It should be noted that the modified metadata includes: undoing metadata, added metadata, and metadata that has undergone changes. In a certain application scenario described in this specification, the metadata designer decrypts the metadata in the distributed version control system and imports it into the database. Then, all business metadata can be displayed on the front end. Users can then select any metadata for operation and processing, and the designer will first synchronize the changes to the database. It should also be noted that the designer will display all modified metadata for developers' reference. Developers can choose any time and place to commit or undo changes to the distributed version control system for metadata synchronization, meaning the designer will reverse-synchronize the metadata state in the database back to the distributed version control system.

[0069] Furthermore, after obtaining the changed metadata by modifying the metadata in the preset database through the preset designer, the method also includes the following steps:

[0070] First, the metadata branch containing the changed metadata in the pre-built database needs to be processed using a preset program to obtain a metadata patch resource file. Then, the metadata patch resource file is deployed to the development environment corresponding to the newly created project using a pre-built patching tool. That is, when the project is completed and meets the conditions for release, developers can choose to release the project and generate usable resource files. The content of the resource files is encrypted and therefore unreadable externally, ensuring the security of the patch. The metadata patch resource file can be used for project updates and deployments to fix problems. This ensures the security of the development system's metadata and patch resource file data. A unified development project workflow and patch creation workflow provide convenience and save development costs for various business systems.

[0071] Furthermore, after processing the metadata branch containing the changed metadata in the pre-configured database according to a preset program to obtain the metadata patch resource file, the method also includes the following steps:

[0072] The metadata patch resource file is published according to a preset procedure. By analyzing the changed metadata in the published metadata patch resource file, the problem patch corresponding to the current project is identified, and the problem patch is updated and upgraded to fix the current project. In other words, in a certain application scenario described in this manual, the project can select the problem patch that needs to be fixed based on the published patch metadata, update and upgrade the patch, and then fix the corresponding problem.

[0073] S103: Process the metadata branch in the preset database according to a preset program to obtain a metadata resource file, and publish and deploy the metadata resource file to the development environment corresponding to the new project.

[0074] Based on the above steps, after adding a database as a transit center between the distributed version control system and the designer, the designer no longer directly connects to Git, but instead connects to the database content. This significantly reduces batch file lookups and updates, simplifying metadata operations. To increase the security of metadata publishing, the designer decrypts and maps the metadata to the database before the current metadata can be published and deployed. One or more embodiments in this specification will process the metadata branches in the pre-set database based on a preset program during the deployment process. The program can publish the metadata of the current Git branch displayed in the database, creating a resource metadata file, and then publishing and deploying the metadata resource file to the development environment corresponding to the newly created project.

[0075] This embodiment of the specification introduces a database as a central hub for metadata processing. The database maps metadata to the distributed version control system, a metadata designer manipulates and processes this metadata mapping, and finally, the metadata designer reverse-synchronizes the database metadata back to the distributed version control system, publishing and deploying the metadata. Encryption of the metadata ensures project data security, and reliable deployment guarantees the tamper-proof capability of patches.

[0076] like Figure 3 As shown, this specification provides a schematic diagram of the internal structure of a dynamic metadata deployment device according to one or more embodiments. Figure 3 As can be seen from one or more embodiments of this specification, a dynamic deployment apparatus for metadata includes:

[0077] A binding unit is used to obtain a newly created project from the preset designer and bind the newly created project to a preset distributed version control system; wherein, the preset distributed version control system controls the branching and historical versions of metadata;

[0078] The decryption unit is used to map the corresponding metadata branch in the preset distributed version control system to the preset database based on the preset designer, and decrypt the metadata branch in the preset database through the preset designer;

[0079] The deployment unit is used to process the metadata branches in the pre-set database based on a preset program to obtain metadata resource files, and then deploy the metadata resource files to the development environment corresponding to the newly created project.

[0080] Furthermore, in one or more embodiments of this specification, the device further includes an encryption unit, which is used to encrypt metadata based on a preset encryption strategy to obtain encrypted metadata, and to manage and control the encrypted metadata through a preset distributed version control system.

[0081] The encryption unit specifically includes:

[0082] A construction unit is used to obtain one or more resource information corresponding to each of the metadata branches in the threshold distributed version control system, and to construct the access structure of each of the metadata branches based on the inclusion relationship of the one or more resource information.

[0083] The branch encryption unit is used to encrypt each metadata branch based on the master public key of each metadata branch and the access structure of each metadata branch, so as to obtain the encrypted metadata.

[0084] Furthermore, in one or more embodiments of this specification, the decryption unit specifically includes:

[0085] The acquisition unit is used to acquire the current project corresponding to the preset designer, so as to monitor and acquire the resource information of the current project operation;

[0086] A branch decryption unit is used to obtain the master private key of the preset designer, and to decrypt the metadata branch in the preset database based on the master private key and the resource information of the current project operation;

[0087] If the master private key corresponds to the master public key and the resource information of the current project operation conforms to the access structure, then the decryption of the metadata branch in the preset database is realized.

[0088] Furthermore, in one or more embodiments of this specification, the apparatus further includes:

[0089] The determining unit is used to determine the metadata to be changed in the preset database based on the current project corresponding to the newly created project;

[0090] The data acquisition unit is used to modify the metadata in the preset database through the preset designer to obtain modified metadata; wherein, the modified metadata includes: revoked metadata, added metadata, and transformed metadata;

[0091] A synchronization unit is used to synchronize the changed metadata to the distributed version control system through the preset designer.

[0092] Furthermore, in one or more embodiments of this specification, the apparatus includes:

[0093] The processing unit is used to process the metadata branch containing the changed metadata in the preset database according to a preset program to obtain a metadata patch resource file;

[0094] The patch deployment unit is used to deploy the metadata patch resource file to the development environment corresponding to the newly created project based on the pre-built patch tool.

[0095] Furthermore, in one or more embodiments of this specification, the apparatus further includes:

[0096] The publishing unit is used to publish the metadata patch resource file according to a preset procedure;

[0097] The update unit is used to determine the problem patch corresponding to the current project by using the changed metadata in the published metadata patch resource file, so as to update and upgrade the problem patch and realize the processing and repair of the current project.

[0098] Furthermore, in one or more embodiments of this specification, the apparatus further includes:

[0099] The judgment unit is used to determine whether there is a metadata dependency between the newly created project and the pre-set distributed version control system; if there is, the metadata dependency is obtained and written into the newly created project to process the metadata dependency.

[0100] like Figure 4 As shown, this specification provides an internal structure diagram of a dynamic metadata deployment device in one or more embodiments. Figure 4 As can be seen from one or more embodiments of this specification, a dynamic deployment device for metadata includes:

[0101] At least one processor; and,

[0102] A memory communicatively connected to the at least one processor; wherein,

[0103] 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:

[0104] Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata;

[0105] The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer;

[0106] The metadata branches in the pre-set database are processed according to a preset program to obtain metadata resource files, which are then deployed to the development environment corresponding to the newly created project.

[0107] like Figure 5 As shown, this specification provides a schematic diagram of the internal structure of a non-volatile storage medium according to one or more embodiments. Figure 5 As shown in one or more embodiments of this specification, a non-volatile storage medium stores computer-executable instructions, which are capable of:

[0108] Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata;

[0109] The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer;

[0110] The metadata branches in the pre-set database are processed according to a preset program to obtain metadata resource files, which are then deployed to the development environment corresponding to the newly created project.

[0111] 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.

[0112] 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.

[0113] 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 method for dynamically deploying metadata, characterized in that, The method includes: Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata; The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer; The metadata branches in the pre-set database are processed based on a preset program to obtain metadata resource files, which are then published and deployed to the development environment corresponding to the new project. Before obtaining the new project from the preset designer and binding the new project to the preset distributed version control system, the method further includes: The metadata is encrypted based on a preset encryption strategy to obtain encrypted metadata, and the encrypted metadata is managed and controlled through a preset distributed version control system. Specifically, the step of encrypting the metadata based on a preset encryption strategy to obtain encrypted metadata includes: Obtain one or more resource information corresponding to each of the metadata branches in the pre-set distributed version control system, and construct the access structure of each metadata branch based on the inclusion relationship of the one or more resource information; Based on the master public key of each metadata branch and the access structure of each metadata branch, each metadata branch is encrypted to obtain the encrypted metadata.

2. The method for dynamically deploying metadata according to claim 1, characterized in that, Decrypting the metadata branch in the preset database using the preset designer specifically includes: Obtain the current project corresponding to the preset designer, and monitor and obtain the resource information of the current project operation; Obtain the master private key of the preset designer, and decrypt the metadata branch in the preset database based on the master private key and the resource information of the current project operation; If the master private key corresponds to the master public key and the resource information of the current project operation conforms to the access structure, then the decryption of the metadata branch in the preset database is realized.

3. The method for dynamically deploying metadata according to claim 2, characterized in that, After decrypting the metadata branch in the preset database using the preset designer, the method further includes: Based on the current project corresponding to the newly created project, determine the metadata to be changed in the preset database; The metadata in the preset database is modified by the preset designer to obtain modified metadata; wherein, the modified metadata includes: undo metadata, add metadata, and transform metadata; The modified metadata is synchronized to the distributed version control system via the preset designer.

4. The method for dynamically deploying metadata according to claim 3, characterized in that, After obtaining the changed metadata by modifying the metadata in the preset database through the preset designer, the method further includes: The metadata branch containing the changed metadata in the preset database is processed according to a preset program to obtain a metadata patch resource file; The metadata patch resource file is deployed to the development environment corresponding to the newly created project using a pre-built patching tool.

5. The method for dynamically deploying metadata according to claim 4, characterized in that, The After processing the metadata branch containing the changed metadata in the preset database according to a preset program to obtain the metadata patch resource file, the method further includes: The metadata patch resource file is published according to a preset procedure; By analyzing the changed metadata in the published metadata patch resource file, the problem patch corresponding to the current project is identified, and the problem patch is updated and upgraded to achieve the processing and repair of the current project.

6. The method for dynamically deploying metadata according to claim 1, characterized in that, After obtaining the new project from the pre-built designer and binding the new project to the pre-built distributed version control system, the method further includes: Determine whether there is a metadata dependency between the newly created project and the pre-built distributed version control system; If it exists, the metadata dependency is obtained and written into the new project to process the metadata dependency.

7. A dynamic deployment device for metadata, characterized in that, The device includes: A binding unit is used to obtain a newly created project from the preset designer and bind the newly created project to a preset distributed version control system; wherein, the preset distributed version control system controls the branching and historical versions of metadata; The decryption unit is used to map the corresponding metadata branch in the preset distributed version control system to the preset database based on the preset designer, and decrypt the metadata branch in the preset database through the preset designer; The deployment unit is used to process the metadata branches in the preset database based on a preset program to obtain metadata resource files, and then deploy the metadata resource files to the development environment corresponding to the new project. Before obtaining the new project from the pre-built designer and binding the new project to the pre-built distributed version control system, the method further includes: The metadata is encrypted based on a preset encryption strategy to obtain encrypted metadata, and the encrypted metadata is managed and controlled through a preset distributed version control system. Specifically, the step of encrypting the metadata based on a preset encryption strategy to obtain encrypted metadata includes: Obtain one or more resource information corresponding to each of the metadata branches in the pre-set distributed version control system, and construct the access structure of each metadata branch based on the inclusion relationship of the one or more resource information; Based on the master public key of each metadata branch and the access structure of each metadata branch, each metadata branch is encrypted to obtain the encrypted metadata.

8. A dynamic deployment device for metadata, comprising: 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: Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata; The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer; The metadata branches in the pre-set database are processed based on a preset program to obtain metadata resource files, which are then deployed to the development environment corresponding to the new project. Before obtaining the new project from the pre-built designer and binding the new project to the pre-built distributed version control system, the method further includes: The metadata is encrypted based on a preset encryption strategy to obtain encrypted metadata, and the encrypted metadata is managed and controlled through a preset distributed version control system. Specifically, the step of encrypting the metadata based on a preset encryption strategy to obtain encrypted metadata includes: Obtain one or more resource information corresponding to each of the metadata branches in the pre-set distributed version control system, and construct the access structure of each metadata branch based on the inclusion relationship of the one or more resource information; Based on the master public key of each metadata branch and the access structure of each metadata branch, each metadata branch is encrypted to obtain the encrypted metadata.

9. A non-volatile storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are capable of: Obtain a new project from the pre-built designer and bind the new project to the pre-built distributed version control system; wherein the pre-built distributed version control system controls the branching and historical versions of metadata; The corresponding metadata branch in the pre-built distributed version control system is mapped to the pre-built database based on the pre-built designer, and the metadata branch in the pre-built database is decrypted through the pre-built designer; The metadata branches in the pre-set database are processed based on a preset program to obtain metadata resource files, which are then deployed to the development environment corresponding to the new project. Before obtaining the new project from the pre-built designer and binding the new project to the pre-built distributed version control system, the method further includes: The metadata is encrypted based on a preset encryption strategy to obtain encrypted metadata, and the encrypted metadata is managed and controlled through a preset distributed version control system. Specifically, the step of encrypting the metadata based on a preset encryption strategy to obtain encrypted metadata includes: Obtain one or more resource information corresponding to each of the metadata branches in the pre-set distributed version control system, and construct the access structure of each metadata branch based on the inclusion relationship of the one or more resource information; Based on the master public key of each metadata branch and the access structure of each metadata branch, each metadata branch is encrypted to obtain the encrypted metadata.

Images