Skip to content

Handle deploy lock ownership fallback when meza-ansible is missing#76

Open
arpitjain099 wants to merge 1 commit into
nasa:mainfrom
arpitjain099:fix-repo-info-parse-74
Open

Handle deploy lock ownership fallback when meza-ansible is missing#76
arpitjain099 wants to merge 1 commit into
nasa:mainfrom
arpitjain099:fix-repo-info-parse-74

Conversation

@arpitjain099

Copy link
Copy Markdown

This keeps meza deploy from crashing on minimal hosts where the meza-ansible account is not available yet.\n\nI kept the lock ownership behavior the same where possible, but made the fallback path resilient:\n- if meza-ansible is missing, use the current user\n- keep group preference order apache, www-data, then wheel\n- if none of those groups exist, use the current process group\n\nI also added a regression test that covers the failing path from #74.\n\nTests run:\n- python3 -m unittest tests/unit/test_deploy_lock_fallback.py\n- python3 -m py_compile src/scripts/meza.py tests/unit/test_deploy_lock_fallback.py\n\nFixes #74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant