-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
Autodeploy: optionally fix file permissions #343
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks !
Humm, funny this permission problem is the root cause since |
I think this fixes #342 |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/1646/Result : failure BIRDHOUSE_DEPLOY_BRANCH : autoupdate-permission-fix DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-20.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1185/NOTEBOOK TEST RESULTS |
I just double checked and unfortunately it does not fix that issue |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/1683/Result : failure BIRDHOUSE_DEPLOY_BRANCH : autoupdate-permission-fix DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-133.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1200/NOTEBOOK TEST RESULTS |
Overview
The autodeploy mechanism creates new files owned by root. If this is not desired then users have to manually update the file ownership after each autodeployment. This adds an option to change the ownership of all files to a specific user after each autodeployment.
For example, if the code in this repo is currently owned by a user named
birduser
with uid 1002, then by settingexport AUTODEPLOY_CODE_OWNERSHIP="1002:1002"
inenv.local
, all files and folders in this repo will continue to be owned bybirduser
after each autodeployment.Changes
Non-breaking changes
adds an optional environment variable to env.local
Breaking changes
None
Related Issue / Discussion
Additional Information