on 2018 Oct 04 9:07 PM
I'm looking to understand what are the best practices and pros/cons for using only one tenant for Cloud Integration for prod and non-prod environments. Technically, it seems possible, but why is it advised or not?
Thanks!
Request clarification before answering.
Hello,
I can think of some cons of using only one tenant for PROD and NON-PROD environments:
- Some prepackaged content (configure-only) would use non-configurable endpoints in the iflows. This would prevent the deployment of copies of this iflow at the same time (e.g. for TEST and PROD). However when these cases are identified we usually recommend opening a support incident to make the endpoint configurable as it is a easy fix.
- When something goes wrong with a TEST implementation/deployment that would affect the whole tenant (OOM, deadlocks, etc), PROD would also be affected.
Best Regards,
Carlos
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
53 | |
10 | |
9 | |
8 | |
6 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.