Save mapping to file (Deprecated)

How to save a network mapping for repeated use

After a mapping was created or modified and validated in the Network tab, it is highly recommended to save it into file.

The code integration view from within the Network tab

In order to update a mapping, click the "UPDATE" button within the code integration view. Clicking it would create a new version of your code integration script, that includes a new leap_mapping.yaml.

The code integration view expanded to show the created leap_mapping.yaml file

This file would ensure this mapping could be applied to new models uploaded to the platform of the same architecture. In order to ensure future CLI code uploads would also include this leap_mapping.yaml is it highly recommended to download this file to the local environment.

Downloading the leap_mapping.yaml

• The easiest way to download the mapping file is by going to the network wizard and reviewing it. Once assets are visualized, the option to "Download mapping file" should be available from the dropdown menu.

The option to download a mapping file from the Network Wizard

• Using the CLI leap code pull option would pull the current code into your local repository (inside a folder with the name of your code integration script). You can then locate the leap_mapping.yaml file and copy it into the root of your project

• Copy Pasting the entire file from the extended code integration view is also possible if the other two options are not available.

Once this file is downloaded placing it within the root folder of your integration script where the leap.yaml is located would ensure any future upload of a model would have this mapping automatically applied to it.

Note that in case you change architecture or upgrade your server, you might need to create this mapping file again. In that case, uploading models would result in errors. If that happens, we recommend deleting or renaming the mapping file so it would not be automatically applied when uploading a new model.