aws / aws/ec2-image-builder-roadmap
[BUG] Cannot use setgid permissions with CreateFolder (e.g. permissions: 2750)
- Dominant language
- No language data
- Stars
- 35
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
What do you want us to build?
When using setuid, setgid, or stickybit permisisons on a folder, you will get this error:
```
CreateFolder: [ ERROR ] Encountered permissions error given permission '2750' does not lie between 0 and 777
```
I have not tested with a file but I am willing to bet the same issue will apply.
The docs show the permissions default value as `0777` which leads one to believe `2750` would be supported. Either update the docs to show only `777` or allow the use of setuid, setgid, and stickybit.
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
I am trying to set setgid permissions for a folder in Linux.
**Are you currently working around this issue?**
How are you currently solving this problem?
I create the folder using `CreateFolder` then run `ExecuteBash` to set the proper permissions. I may stop using `CreateFolder` due to this limitation.
**Additional context**
Anything else we should know?
This should also be tested with files. I suspect this to be the same issue with them.
Contributor guide
Research direction
Start by tracing the CreateFolder permission validation and compare it with the documented default of 0777; the issue also names ExecuteBash as the current workaround. Check whether the same validation affects files, then verify that setuid, setgid, and sticky-bit permissions are either accepted or explicitly documented as unsupported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, linux
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100