Hi,
We have recently tried local development and deployment using ApigeeX.
As this new approach supports archived deployment on environments that are marked as "archived" during creation. We want to know how will this approach fit in to the overall CI/CD and environment mgt. strategy for an Organization.
Some points of consideration are -
- Maven Deployment Tool
- Integ. Test Cases
- Different git repos for each proxy/shared flow
- how many workspaces to be maintained
- Propagating proxies to higher environments
Is it recommended to keep both set of environments like lower environments as archived and higher ones as non-archived.
Any thoughts in this direction are welcomed.
@ssvaidyanathan @dchiesa1 please share some inputs
thanks!!