Add support for exporting and importing all entities

[jensalm]

Allow the cli to export and import all entities. The export should not contain instance specific details like ids, when it was created, etc.
The output from export should be able to be imported in an empty ziti instance.
Output should support both json and yaml.

Example:

  "identities": [
    {
      "appData": {},
      "authPolicy": "@Default",
      "disabled": false,
      "externalId": null,
      "isAdmin": true,
      "isDefaultAdmin": false,
      "isMfaEnabled": false,
      "name": "Test 1",
      "roleAttributes": [],
      "tags": {},
      "typeId": "Default"
    }
  ],
  "configs": [
    {
      "data": {
        "addresses": [
          "google.ziti"
        ],
        "portRanges": [
          {
            "high": 120,
            "low": 80
          }
        ],
        "protocols": [
          "tcp"
        ]
      },
      "name": "test 1 intercepting config",
      "tags": {},
    }
  ]
  "services": [
    {
      "configs": [
        "@test 1 intercepting config"
      ],
      "encryptionRequired": true,
      "name": "test 1",
      "roleAttributes": [
        "services"
      ],
      "tags": {},
      "terminatorStrategy": "smartrouting"
    }
  ]

[qrkourier]

What's an example use case for the feature? By recreate do you mean clone to a fresh network as opposed to managing a Ziti network's entities?

[jensalm]

What's an example use case for the feature? By recreate do you mean clone to a fresh network as opposed to managing a Ziti network's entities?

Basic use case is to be able to "clone" a network.

[mvarchdev]

Also I was looking for this. It would be nice not only to export/import entities but also policies and basically configuration at its whole. Lets say I have dev team that want to replicate env, or I have application and I want to store roles/policies per-app/per-service and just sync it from git...

[dovholuknf]

Hi @mvarchdev - that's exactly what @jensalm PR will do/does. see: #2571

[qrkourier]

Let's distinguish between cloning (import/export) and configuration management. The forthcoming tool has import/export, but not configuration management.

The difference is one-shot import vs. as-code management, e.g., gitops. Configuration management usually means you express the desired state in some file, probably under version control, and the config system reconciles that desired state with the actual state. For that, you'd probably use Kubernets CRDs, Ansible, Terraform, Pulumi, Salt Stack, etc.