Skip to content

fix: Enforce ownership of deployed project in sandbox environment #1503

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.

Sign up for GitHub

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

Draft
wants to merge 2 commits into
base: development
Choose a base branch
from
Draft

fix: Enforce ownership of deployed project in sandbox environment #1503

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
92b855d
Enforce setting the deployed project directory and contents as being …
howard-e Aug 26, 2025
b8db51b
Merge branch 'development' into sandbox-deployment-permissions-fix
howard-e Aug 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions deploy/roles/application/tasks/upload-source-code.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,3 +52,16 @@
validate: 'visudo -cf %s'
become: yes
when: deployment_mode != 'development'

# On sandbox, users have their own accounts (but can be elevated to root).
# When code sync happens, files end up owned by the deploying user, but the
# application runs as aria-bot user and needs consistent ownership regardless
# of who deployed. This task ensures proper ownership by the `application_user`.
- name: Fix file ownership for sandbox environment
file:
path: '{{source_dir}}'
owner: '{{application_user}}'
group: '{{application_user}}'
recurse: yes
become: yes
when: deployment_mode == 'sandbox'
Loading