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

Permissions on galaxy directory during privilege separation + NGINX access #114

Open
hexylena opened this issue Jul 14, 2020 · 0 comments
Open
Labels

Comments

@hexylena
Copy link
Member

During deployment with priv-sep, the permissions for the galaxy directory can become too restrictive.

Overriding them with

--extra-vars "__galaxy_dir_perms='0755'"

solves the issue, but, it is sub-optimal for new admins.

It is set due to

__galaxy_dir_perms: "{{ '0750' if __galaxy_user_group == __galaxy_privsep_user_group else '0755' }}"

But for EU (and others), we have it set such that:

galaxy_separate_privileges: true
galaxy_group: galaxy
galaxy_system_group: galaxy

Thus, given

__galaxy_user_group: "{{ ((galaxy_group | default({})).name | default(galaxy_group)) if galaxy_group is defined else (__galaxy_group_result.results[0].ansible_facts.getent_group.keys() | first) }}"
__galaxy_privsep_user_group: "{{ ((galaxy_group | default({})).name | default(galaxy_group)) if galaxy_group is defined else (__galaxy_group_result.results[1].ansible_facts.getent_group.keys() | first) }}"

In both cases, the galaxy_group variable is set, and so those values are equivalent. But it doesn't account for the fact that nginx still needs access.

@hexylena hexylena added the bug label Jul 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant