英文:
Mirgrate from apigee edge to apigee x
问题
有人知道如何从apigee edge
迁移到apigee X
吗?我的意思是迁移所有代理、应用程序、共享流、KVM、目标服务器、缓存等。
英文:
Does anybody has any idea on how to migrate from apigee edge
to apigee X
. By that I mean migrating all the proxy, apps, shared-flows, KVMs, Target servers, cache etc.
答案1
得分: 2
有一个名为Apigee sackmesser工具,它可以从Edge或X中导出配置。
Apigee Sackmesser允许您使用导出命令导出组织,包括组织和环境配置,代理和共享流程。
sackmesser export --apigeeapi -u "$APIGEE_USER" -p "$APIGEE_PASS" -o "$APIGEE_ORG"
使用部署命令,您可以迭代导出的代理或指向特定配置,将它们部署到另一个平台。
然而,由于这不是设计成完全自动化迁移工具,因此存在某些限制,比如它不支持以下迁移功能:
-
加密KVM条目的迁移(无法导出)。
-
密钥库的迁移(证书无法导出)。
-
共享流程(sf)的依赖解析(如果sf A使用sf B,则需要在sf A之前部署sf B)。
-
规范的导出。
因此,使用上述工具,您可以使用导出和部署命令从APIGEE Edge迁移代理、应用密钥和其他一些数据到APIGEE X。
英文:
There is an Apigee sackmesser tool that can export configuration from Edge or X.
Apigee Sackmesser lets you export an Organization including org and env configs, proxies and shared flows with the export command
sackmesser export --apigeeapi -u "$APIGEE_USER" -p "$APIGEE_PASS" -o "$APIGEE_ORG"
With the deploy command you can then iterate through the exported proxies or point at a specific config to deploy them to another platform.
However, there are certain limitations as this is not designed to serve as a fully automated migration tool as it lacks migration features like:
-
Migration of encrypted KVM entries (can't be exported).
-
Migration of Keystores (Certs can't be exported).
-
Shared flow(sf) dependency resolution (if sf A uses sf B then sf B needs to be deployed before sf A).
-
Export of specs.
So with the above tool you can migrate Proxies, App keys and a few other data from APIGEE edge to APIGEE x with export and deploy commands.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库,让每个人都能够通过互相帮助和分享经验来进步。
评论