Exporting and importing Axons in Algoreus

• Exporting Data Axons

• Importing Data Axons

You can import and export data axons in the Algoreus Genesis.

There are multiple reasons you might want to export axons, such as sharing them with other developers, maintaining version control, or transferring them from a development environment to a testing or production environment. For instance, you might have completed the development and debugging of an axon set and want to deploy them to a production environment. In such a case, you would export the axons, integrate them into version control, and then use the Lifecycle Microservices to deploy them to a production environment.

---

Exporting Data Pipelines

Axons can be exported from the Algoreus Genesis, Axons List page, or Deploy Axon in Axon page.

When you export an axon, Algoreus saves the axon configuration as a JSON file on your local drive. The JSON file includes all the node configurations and axon configurations, including comments.

All exported axon are in the DRAFT state. This means that an exported axons doesn't include any triggers, schedules, or axons configurations created after deployment. If these are necessary, you will have to recreate them.

Note: For details on exporting all deployed data axons across all namespaces, select, "Export All Application Details". For exporting a single data axon in a namespace, select, "Details of an Application". For exporting all axons in a namespace, select, "List Applications".

---

Importing Data Axons

Follow these steps to import an Axon in the Algoreus Genesis:

1. Click Import.

2. Upload the JSON file that was saved when you exported the axon.

3. (Optional) You may be prompted to upgrade your node versions. If so, click Fix all. If a particular node is not found, follow the prompts to install it from the Hub.

4. (Optional) If the axon employs an older version of a node and if that node version exists in the current Algoreus instance, you can continue using the old version or upgrade to the current version that matches the instance/namespace version.

5. (Optional) If you use a custom node in your axon and you receive a prompt in the upgrade window indicating that the node wasn't found, you need to deploy that custom node first and then re-import the axon.

6. The imported axon will open in the Algoreus Genesis page.

7. Click Save to keep the axon as a Draft.

The axon will then appear under Drafts in the Axons List page.

---