- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-07-2023 03:57 AM
Hi everyone, we are a small team of 3 and trying to understand if we request more resources than necessary from our admins. We all have our own xsoar instances for development because we don't want to write to the same automation someone else is working on , basically we want isolation. Multi tenancy allows tenant level content upload but there is no way to edit indicator types in tenants that's the main reason why we don't use multi tenancy in our dev environment (we have multi tenant license).
Do you also have separate xsoar instances for each developer?
03-07-2023 04:55 AM
Hi! Typically what we see people do is prepend their initials so anything they write is named uniquely. The advantages to this would be that if your co-worker created a nice automation you wanted to leverage you don't have to get it from them and load it in your environment. You can also see examples of others work. The advantage of having your own complete environment is that you can make big mistakes that delay server response or even crash and you haven't impacted someone else. Also if you are trying to measure impact by monitoring server resources you don't have to worry that a coworker is running something at the same time. I agree that Multi-tenant wouldn't be a great solution for you but if you have a heavily active development team working in parallel there could be advantages to having your own development server.
03-10-2023 09:19 AM
prepending initials makes sense I think we can handle that. Thank you for your advice 🙂
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!