Apigee supports creating branches of API proxies to allow for feature-based development

 • Branch by Feature - In Apigee, you can create branches of an API proxy for different features or capabilities. For example:

• master branch: Main production API proxy
• new_feature branch: Version with new feature added
• bugfix_123 branch: Version for fixing a specific bug

• Independent Development - Each branch can be developed independently. Developers working on different features can work in separate branches.

• Targeting Environments - You can deploy a branch to a specific environment, like:

• master branch to production environment
• new_feature branch to test and staging environments

• Merge Changes - After testing a feature branch, you can merge the changes back into the master branch. Apigee provides tools to assist with merging branches.

• Snapshots - You can create snapshots of an API proxy to capture its state at a point in time. This allows reverting to a known good snapshot if needed.

• Isolation - Different branches are isolated, so changes in one branch do not affect others. This reduces the risk of breaking the main production API.

• Access Control - Apigee allows configuring permissions to control which users can access, deploy, and manage specific API proxy branches.

• Versioning - Apigee supports API versioning, so API proxies in different branches can implement different API versions simultaneously.

• Roll Back - If an API deployment from a branch has an issue, you can easily roll back to the previous stable version.

In summary, Apigee's branching feature - combined with its environment and deployment tools - allows for an effective feature branch workflow to manage the lifecycle of your APIs. Let me know if you have any other questions!