DiamondLightSource / DiamondLightSource/mx-bluesky
Deploy script is not setting permissions correctly
- Dominant language
- Python
- Stars
- 4
- Forks
- 5
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 2
Description
When running the hyperion deployment script @jacob720 ended up deploying something where permissions were wrong on the `mx-bluesky` folder (even though they were correct on child folders) e.g.
```
[ffv81422@ws455 helm]$ pwd
/dls_sw/i03/software/bluesky/mx-bluesky_1.5.16/mx-bluesky/helm
[ffv81422@ws455 helm]$ getfacl .
# file: .
# owner: hvj62882
# group: dls_dasc
# flags: -s-
user::rwx
group::rwx
other::r-x
[ffv81422@ws455 helm]$ cd ..
[ffv81422@ws455 mx-bluesky]$ pwd
/dls_sw/i03/software/bluesky/mx-bluesky_1.5.16/mx-bluesky
[ffv81422@ws455 mx-bluesky]$ getfacl .
# file: .
# owner: hvj62882
# group: dls_dasc
# flags: -s-
user::rwx
group::r-x
other::r-x
```
This may have been NetApp issues
## Acceptance Criteria
- Deployment script will set permissions correctly
Contributor guide
Research direction
Locate the hyperion deployment script and reproduce the deployment described in the issue. Use getfacl to compare permissions on the mx-bluesky folder and its child folders, then determine whether the script sets the parent directory correctly. Done means the deployment script consistently applies the expected permissions to the deployed folder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100