Multi-cloud data processing and integration

1. A method, comprising:

receiving, by a device, a request to merge a first cloud computing instance with a second cloud computing instance to generate a multi-cloud computing instance;

accessing, by the device, a first application programming interface to obtain a first configuration of the first cloud computing instance,

wherein the first configuration of the first cloud computing instance is associated with first metadata in a first format identifying a first set of values for a set of attributes of the first cloud computing instance;

accessing, by the device, a second application programming interface to obtain a second configuration of the second cloud computing instance,

wherein the second configuration of the second cloud computing instance is associated with second metadata in a second format identifying a second set of values for the set of attributes;

selecting, by the device, a source configuration for one or more conflicting values for attributes of the set of attributes;

generating, by the device, a target configuration for an integrated multi-cloud using the source configuration for the one or more conflicting values for attributes and a mutually identified configuration for one or more non-conflicting values for attributes of the set of attributes; and

instantiating, by the device, a set of resources with the target configuration for the multi-cloud computing instance; and

providing, by the device, output identifying the multi-cloud computing instance.

2. The method of claim 1 , further comprising:

merging the first metadata and the second metadata into a third format; and

storing the first metadata and the second metadata in the third format in a data structure.

3. The method of claim 2 , further comprising:

identifying a merge error in the multi-cloud computing instance;

retrieving the first metadata or the second metadata from the data structure based on identifying the merge error; and

altering, based on the first metadata or the second metadata, the target configuration of the multi-cloud computing instance to revert the merge error.

4. The method of claim 1 , further comprising:

receiving information identifying a third configuration of a third cloud computing instance,

wherein the third configuration of the third cloud computing instance is associated with third metadata identifying a third set of values for the set of attributes; and

merging the third set of values into the target configuration based on the source configuration.

5. The method of claim 1 , wherein the set of attributes includes at least one of:

a set of objects,

a set of applications,

a set of tabs,

a set of groups,

a set of queues,

a set of templates,

a set of processes,

a set of pages,

a set of classes,

a set of profiles, or

a set of permissions.

6. The method of claim 1 , further comprising:

merging the first metadata or the second metadata to a third metadata format using a metadata conversion engine,

wherein the third metadata format differs from the first metadata and the second metadata with regard to one or more attributes; and

wherein generating the target configuration comprises:

generating the target configuration from the third metadata format.

7. The method of claim 6 , wherein merging the first metadata or the second metadata comprises:

tokenizing the first metadata or the second metadata into a set of tokens;

parsing the set of tokens using a metadata syntax parser to identify a metadata syntax associated with the set of tokens;

determining that the metadata syntax associated with the set of tokens is error-free; and

outputting data associated with the metadata syntax based on determining that the metadata syntax is error-free.

8. A device, comprising:

one or more memories; and

one or more processors, coupled to the one or more memories, configured to:

receive training data for merging metadata,

wherein the training data includes data identifying a set of merged cloud computing instances associated with metadata in a set of formats; and

train a metadata merging model for merging metadata using the training data for merging metadata;

receive a request to merge a first cloud computing instance with a second cloud computing instance to generate a multi-cloud computing instance;

access a first application programming interface to obtain a first configuration of the first cloud computing instance,

wherein the first configuration of the first cloud computing instance is associated with first metadata in a first format identifying a first set of values for a set of attributes of the first cloud computing instance;

access a second application programming interface to obtain a second configuration of the second cloud computing instance,

wherein the second configuration of the second cloud computing instance is associated with second metadata in a second format identifying a second set of values for the set of attributes;

select a source configuration for one or more conflicting values for attributes of the set of attributes;

generate, using the metadata merging model, a target configuration for an integrated multi-cloud using the source configuration for the one or more conflicting values for attributes and a mutually identified configuration for one or more non-conflicting values for attributes of the set of attributes; and

instantiate a set of resources with the target configuration for the multi-cloud computing instance; and

provide output identifying the multi-cloud computing instance.

9. The device of claim 8 , wherein the one or more processors, to generate the target configuration, are configured to:

identify a dominant state for a metadata type;

select, from the first metadata and the second metadata, an attribute value corresponding to the dominant state; and

include the attribute value in the target configuration.

10. The device of claim 8 , wherein the one or more processors are further configured to:

identify a set of compatibility rules; and

wherein the one or more processors, to generate the target configuration, are configured to:

generate the target configuration based on the set of compatibility rules.

11. The device of claim 8 , wherein the one or more processors are further configured to:

identify an attribute, of the set of attributes, without a value in the first metadata or the second metadata; and

determine a default attribute value for the attribute; and

wherein the one or more processors, to generate the target configuration, are configured to:

generate the target configuration based on the default attribute value.

12. The device of claim 8 , wherein the one or more processors, to train the metadata merging model, are configured to:

train a set of parsers for a set of attributes corresponding to a set of metadata types; and

wherein the one or more processors, to generate the target configuration, are configured to:

parse the set of attributes using the set of parsers to identify which values from the first metadata and the second metadata to include in the target configuration.

13. The device of claim 8 , wherein the one or more processors, to generate the target configuration, are configured to:

generate a configuration table;

fill the configuration table with values from the first metadata or the second metadata; and

generate third metadata in a third format based on the configuration table.

14. The device of claim 13 , wherein the one or more processors, to instantiate the set of resources, are configured to:

instantiate the set of resources based on the third metadata.

15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the device to:

receive a request to merge a first cloud computing instance with a second cloud computing instance to generate a multi-cloud computing instance;

access a first application programming interface to obtain a first configuration of the first cloud computing instance,

wherein the first configuration of the first cloud computing instance is associated with first metadata in a first format identifying a first set of values for a set of attributes of the first cloud computing instance;

access a second application programming interface to obtain a second configuration of the second cloud computing instance,

wherein the second configuration of the second cloud computing instance is associated with second metadata in a second format identifying a second set of values for the set of attributes;

select a source configuration for one or more conflicting values for attributes of the set of attributes;

generate a target configuration for an integrated multi-cloud using the source configuration for the one or more conflicting values for attributes and a mutually identified configuration for one or more non-conflicting values for attributes of the set of attributes; and

instantiate a set of resources with the target configuration for the multi-cloud computing instance;

generate a user interface including information identifying a mapping between the target configuration and the first metadata and the second metadata; and

provide the user interface as output identifying the multi-cloud computing instance.

16. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the device to:

receive, via the user interface, a user selection of a dominant state for a metadata type;

select, from the first metadata and the second metadata, an attribute value corresponding to the dominant state; and

include the attribute value in the target configuration.

17. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the device to:

determine a difference metric representing a difference between the first metadata and the second metadata; and

include the difference metric in the user interface.

18. The non-transitory computer-readable medium of claim 17 , wherein the one or more instructions, that cause the device to determine the difference metric, cause the device to:

analyze a first attribute value, of the first set of values, and a second attribute value, of the second set of values, to categorize a difference between the first attribute value and the second attribute value; and

determine the difference metric based on the categorized difference between the first attribute value and the second attribute value.

19. The non-transitory computer-readable medium of claim 15 , wherein a first attribute, of the set of attributes, is related to a second attribute, of the set of attributes, according to a hierarchy; and

wherein the one or more instructions further cause the device to:

identify a first non-conflicting value, of the one or more non-conflicting values and corresponding to the first attribute, and a second non-conflicting value, of the one or more non-conflicting values and corresponding to the second attribute, based on both the first attribute and the second attribute having non-conflicting values and being related according to the hierarchy.

20. The non-transitory computer-readable medium of claim 15 , wherein a first attribute, of the set of attributes, is related to a second attribute, of the set of attributes, according to a hierarchy; and

wherein the one or more instructions further cause the device to:

identify a first conflicting value, of the one or more conflicting values and corresponding to the first attribute, and a second conflicting value, of the one or more conflicting values and corresponding to the second attribute, based on either the first attribute or the second attribute having a conflicting value and being related according to the hierarchy.