How do I validate and deploy the new revision?

 Here are the steps to validate and deploy a new API proxy revision in Apigee after merging a branch:

1. After merging the branch into the master API proxy, the new revision will be unlocked, allowing you to make changes.

2. Make any final tweaks or adjustments needed for the new feature. Test the API calls using the API proxy's test console to ensure everything is working as expected.

3. Promote the revision to a lower environment for testing. In Apigee, environments represent distinct deployment targets:

• Development
• Test
• Staging
• Production

4. Promoting a revision deploys that API proxy version to the selected environment. You'll typically want to promote to:

• Development: For the developer who created the branch
• Test: For more rigorous testing by QA or another team

5. In the lower environments, have additional teams thoroughly test the new feature by exercising all API calls and behavior.

6. If testing passes, lock the revision indicating it is ready for production use. A locked revision should only be changed in case of an emergency fix.

7. Once approved, promote the revision to higher environments:

• Staging: For final validation before production
• Production: To deploy to external clients

8. Monitor API traffic and logs after deployment to identify any issues. Be prepared to roll back to a previous stable revision if needed.

9. Over time, continuously merge new feature branches into the master API proxy to build out your API and services. But always validate and thoroughly test new revisions in lower environments before deploying to production.

That covers the basic workflow for validating, testing and deploying an API proxy revision in Apigee after merging a feature branch. Hopefully this gives you the high level process - let me know if you have any other questions!