Apigee 提供许多不同类型的资源,每种类型都有不同的用途。某些资源只能通过 Apigee 界面、Apigee API 或使用 API 的工具以及由具有必备角色和权限的用户进行配置(即创建、更新和/或删除)。例如,只有属于特定组织的组织管理员才能配置这些资源。这意味着,最终用户无法通过开发者门户配置这些资源,也无法通过任何其他方式配置这些资源。这些资源包括:
API 代理
共享流
API 产品
缓存
KVM
密钥库和信任库
虚拟主机
目标服务器
资源文件
虽然这些资源确实具有受限访问权限,但即使由授权用户对其进行任何修改,历史数据也不会被新数据覆盖。这是因为这些资源仅按当前状态存储在 Apigee 中。此规则的主要例外是 API 代理和共享流。
进行修订版本控制的 API 代理和共享流
API 代理和共享流可通过修订版本进行管理,即创建、更新和部署。修订版本按顺序编号,这样您就可以添加新更改并将其保存为新修订版本,或者通过部署 API 代理/共享流的先前修订版本来还原更改。在任何时候,环境中都只能部署 API 代理/共享流的一个修订版本,除非修订版本具有不同的基本路径。
虽然 API 代理和共享流可通过修订版本进行管理,但如果对现有修订版本进行任何修改,则无法回滚,因为会覆盖旧更改。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-07。"],[[["\u003cp\u003eApigee resources, such as API proxies, shared flows, and KVMs, can only be modified by authorized users through the Apigee UI, APIs, or related tools, and not through developer portals or other means.\u003c/p\u003e\n"],["\u003cp\u003eWhile API proxies and shared flows are managed through revisions, modifications to existing revisions overwrite old changes without a rollback option, and other resources simply update the current data without historical retention.\u003c/p\u003e\n"],["\u003cp\u003eApigee's Audits feature provides information on who performed operations and when, but it does not store older data if resources are updated or deleted, making a separate source control necessary.\u003c/p\u003e\n"],["\u003cp\u003eManaging all Apigee resources, including API proxies and shared flows, in a source control system (SCM) is crucial for data recovery and to avoid potential loss of development work, API request failures, and difficulties in identifying resource interdependencies.\u003c/p\u003e\n"],["\u003cp\u003eThe recommended best practice is to utilize an SCM, often coupled with a CI/CD pipeline, for managing API proxies, shared flows, and other Apigee resources, utilizing Apigee APIs to initially get and subsequently update configurations.\u003c/p\u003e\n"]]],[],null,[]]