Use xinclude to externalize environments/endpoints
We have 5 environments we need to target (CI/CD, DEV, TEST, PROD, SANDBOX). We have 30 apis with new apis on the horizon.
On average each project will require two environments (for the Auth api and the api under test). Rather than have 30 copies of the Auth api details (one for each api) we would prefer to externalize "shared" details via the use of xinclude. That way, when/if the Auth api environment/endpoint details change we only have to apply a single update which will subsequently "trickle down" to all the projects that leverage the shared content.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.