Skip to content
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

[studio] Add a hab user & group to default Studio type. #618

Merged
merged 1 commit into from
Jun 2, 2016

Conversation

fnichol
Copy link
Collaborator

@fnichol fnichol commented Jun 2, 2016

This change coupled with #617 should allow a user to enter a default
Studio and immediately run:

hab start core/redis

without issues.

Neither the Supervisor nor the hab CLI is responsible for adding users
and/groups (at least at the moment) meaning that if a service package
uses a non-privileged user to run under, this could result in a failure.
Further work can be done to have the package announce its user
requirements and have the Supervisor at least detect-and-fail is a user
is not present (minimal solution) or attempt to add a user/group (a
delightful solution).

This change coupled with #617 should allow a user to enter a default
Studio and immediately run:

    hab start core/redis

without issues.

Neither the Supervisor nor the `hab` CLI is responsible for adding users
and/groups (at least at the moment) meaning that if a service package
uses a non-privileged user to run under, this could result in a failure.
Further work can be done to have the package announce its user
requirements and have the Supervisor at least detect-and-fail is a user
is not present (minimal solution) or attempt to add a user/group (a
delightful solution).

Signed-off-by: Fletcher Nichol <[email protected]>
@thesentinels
Copy link
Contributor

By analyzing the blame information on this pull request, we identified @adamhjk to be a potential reviewer

@juliandunn
Copy link
Contributor

LGTM

@thesentinels r+

@thesentinels
Copy link
Contributor

📌 Commit 60fd2ae has been approved by juliandunn

@thesentinels
Copy link
Contributor

⌛ Testing commit 60fd2ae with merge 8276c1c...

thesentinels pushed a commit that referenced this pull request Jun 2, 2016
This change coupled with #617 should allow a user to enter a default
Studio and immediately run:

    hab start core/redis

without issues.

Neither the Supervisor nor the `hab` CLI is responsible for adding users
and/groups (at least at the moment) meaning that if a service package
uses a non-privileged user to run under, this could result in a failure.
Further work can be done to have the package announce its user
requirements and have the Supervisor at least detect-and-fail is a user
is not present (minimal solution) or attempt to add a user/group (a
delightful solution).

Signed-off-by: Fletcher Nichol <[email protected]>

Pull request: #618
Approved by: juliandunn
@thesentinels
Copy link
Contributor

☀️ Test successful - travis

@thesentinels thesentinels merged commit 60fd2ae into master Jun 2, 2016
@fnichol fnichol deleted the fnichol/default-studio-hab-user branch June 2, 2016 03:19
jtimberman pushed a commit that referenced this pull request Jun 12, 2016
This change coupled with #617 should allow a user to enter a default
Studio and immediately run:

    hab start core/redis

without issues.

Neither the Supervisor nor the `hab` CLI is responsible for adding users
and/groups (at least at the moment) meaning that if a service package
uses a non-privileged user to run under, this could result in a failure.
Further work can be done to have the package announce its user
requirements and have the Supervisor at least detect-and-fail is a user
is not present (minimal solution) or attempt to add a user/group (a
delightful solution).

Signed-off-by: Fletcher Nichol <[email protected]>

Pull request: #618
Approved by: juliandunn
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants