<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=479705) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=479705) </details> <!--IssueSummary end--> MR: Pending ## Description Adds ProjectSettings step to the Workspaces Settings Module. - See https://gitlab.com/groups/gitlab-org/-/epics/14186+ for overview and more context - See [Related Issues and MRs section in that epic](https://gitlab.com/groups/gitlab-org/-/epics/14186#related-issues-and-mrs) for related issues and MRs ## Acceptance Criteria - [ ] Adds ProjectSettings step to the Workspaces Settings Module ## Technical Requirements * NOTE: This work should only be necessary if we have not added project-level settings support to the CascadingSettings module - possibly because we have determined that project-level settings must be at a lower precedence level than agent-level settings. * This may require us to focus on different settings which are applicable at both the agent and project level, such as `default_resources_per_workspace_container` and/or `max_resources_per_workspace`, since we may not want to support overriding `max_hours_before_termination_limit` at the project settings level. These different settings do not necessarily have to be added at the CascadingSettings level yet. * This will involve adding a new ProjectSettings step to the Workspaces ROP Settings Module chain * This step will observed the `locked` flag for each relevant setting ## Design Requirements