-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial draft of service group how to docs #672
Initial draft of service group how to docs #672
Conversation
By analyzing the blame information on this pull request, we identified @cwebberOps, @juliandunn and @ryankeairns to be potential reviewers |
It would be good to advise the user that best practice is to name the group |
# Run packages in a service group | ||
A service group is a logical grouping of services with the same package and topology type connected together in a ring. They are created to share configuration and file updates among the services within those groups and can be segmented based on workflow or deployment needs (QA, Production, and so on). Updates can also be [encrypted](/docs/run-packages-security#service-group-encryption) so that only members of a specific service group can decrypt the contents. | ||
|
||
In addition, multiple service groups can reside in the same ring. This allows HTTP API data exposed by supervisors to be shared with other members of the ring regardless of which group they are in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would just remove HTTP API
-- data
is fine
Signed-off-by: David Wrede <[email protected]>
Incorporated feedback and squashed commits. Ready for one last look and then MWR. |
LGTM |
📌 Commit ba0037c has been approved by |
Signed-off-by: David Wrede <[email protected]> Pull request: #672 Approved by: juliandunn
☀️ Test successful - travis |
Signed-off-by: David Wrede <[email protected]> Pull request: #672 Approved by: juliandunn
Signed-off-by: David Wrede [email protected]