-
Notifications
You must be signed in to change notification settings - Fork 521
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
Subset of services experiment #2657
Conversation
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.
Glad to see that it is relatively easy to set up such experiment!
@karolz-ms @BigMorty @ucheNkadiCode @philliphoff -- as an alternative, we could keep just one command and show the service checklist every time; we can do this as an experiment so we're not bothering everybody. We can measure success if people are actually using it; we capture the numerator (number of services selected) and denominator (total number of services). If selected < total, it stands to reason they did make use of the feature; otherwise not. If we saw, for example, that 95% were not using it, then combining commands is probably not the way to go. But if, say, 50% were using it--maybe one command is right. Thoughts? In short, the options are:
|
Interesting idea @bwateratmsft. I could go either way, but I lean towards having the separate menu/command. |
That would be my inclination as well. |
Fixes #2646. This adds a new option to launch a subset of services directly; basically it is equivalent to appending
${serviceList}
to the end of your compose command. This is gated by an experiment.