Due to parallel development, we need to seggregate our services. We don't want to create separate package as we have too many services so if we create separate package then we also need to create separate service as well. Is there any better alternative?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
If we create multiple services in same package then access group will remain same. We have multiple releases so the ruleset belonging to application which belongs to access group needs to be different. So to support parallel development, the only option I can think of creating multiple services (with the same name) but having different service package so that access group will be different. But this will lead to creation of multiple service rules which will facilitate the same process after the final release.