introduce per service settings #122
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wkloucek
force-pushed
the
per-service-settings
branch
from
2e836f3 to
b71ae0b
Compare
wkloucek
force-pushed
the
per-service-settings
branch
from
b71ae0b to
c161c7d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Some settings cannot be configured on a global level and need to be exposed on a per service basis.
In this case:
Related Issue
Motivation and Context
Add the possibility to properly configure oCIS for production deplyoments. One part of it is to assing resources to each services, so that it refects real work usage patterns.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist:
make docs) and committed