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.

Sign up for GitHub

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

Jump to bottom

Allow defining users and groups in software environments #28

Open
MLNW opened this issue Jun 9, 2022 · 0 comments
Open

Allow defining users and groups in software environments #28

MLNW opened this issue Jun 9, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@MLNW
Copy link
Contributor

MLNW commented Jun 9, 2022 •
edited
Loading

A software environment may depend on the existence of users or user groups that need to be created during deployment of the environment. The creation should be idempotent.

For many of the operations in dagos one requires root privileges, e.g. installing a system package. Due to that it would make sense to also tackle #17 at the same time.
@MLNW MLNW mentioned this issue Jun 9, 2022
Open
@MLNW MLNW added the enhancement New feature or request label Jun 9, 2022
MLNW added a commit that referenced this issue Jun 11, 2022
@MLNW
🩹 Store deployed components in /opt/dagos/components
ac663ec 
Before components deployed to a container were stored under
/root/.dagos/components. This affected our BDD test suite which then
picked up on these components.

This change is also a step towards enabling multi user installations by
putting common components to this place and installing them for all
users provisioned during environment deployment.

Relates to #28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MLNW