stackhpc / stackhpc/kayobe-automation
Gitlab permissions are too open for source checkout
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
[WARNING]: Ansible is being run in a world writable directory
392(/builds/crc4/um6p/infrastructure/um6p-kayobe-config), ignoring it as an
393ansible.cfg source. For more information see
394https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-
395world-writable-dir
Options:
- Copy it else where and change permissions
- Change permissions in place
- Get gitlab to checkout with different permissions (nothing immediately obvious in the docs)
- set umask in image to something more restrictive?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files or tests. Start by reading Ansible's world-writable-directory configuration guidance and investigating GitLab checkout permissions or the image umask; done means the source checkout is usable and the warning no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, gitlab, shell
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100